3GPP TS 29244-g30 中英文对照 | 7.2.2 Message Header

学习5G知识，势必要去阅读相关的技术标准，而纯英文的标准协议对于初学者来说是个门槛。

个人在学习5G标准3GPP TS 29244-g30过程中，也发现google的机器翻译实在晦涩难懂，所以个人在借助百度翻译（中国人更懂中文）的同时，人工对每句话进行了校对。

在自己学习的同时，也将翻译内容分享给给广大网友。由于个人能力有限，翻译不到位的地方还请各位网友们指正。

7.2.2 Message Header 消息头

7.2.2.1 General Format 通用格式

PFCP messages use a variable length header. The message header length shall be a multiple of 4 octets. Figure 7.2.2.1-1 illustrates the format of the PFCP Header.

PFCP消息使用可变长度头。消息头长度应为4个八位字节的倍数。PFCP头的格式如图7.2.2.1-1所示。

 

		Bits
Octets		8	7	6	5	4	3	2	1
1		Version			Spare	Spare	FO	MP	S
2		Message Type
3		Message Length (1st Octet) 邮件长度（第一个八位位组）
4		Message Length (2nd Octet) 邮件长度（第二个八位位组）
m to k(m+7)		If S flag is set to "1", then SEID shall be placed into octets 5-12. Otherwise, SEID field is not present at all. 如果S标志被设置为“ 1”，则SEID将被放置在5-12字节中。否则，根本不存在SEID字段。
n to (n+2)		Sequence Number
(n+3)		Spare

Figure 7.2.2.1-1: General format of PFCP Header

图7.2.2.1-1：PFCP标头的常规格式

Where:

- if S = 0, SEID field is not present, k = 0, m = 0 and n = 5;

-如果S = 0，则不存在SEID字段，k = 0，m = 0，n = 5；

- if S = 1, SEID field is present, k = 1, m = 5 and n = 13.

-如果S = 1，则存在SEID字段，k = 1，m = 5，n = 13。

The usage of the PFCP header is defined in clause 7.2.2.4.

PFCP头的用法在第7.2.2.4节中定义。

Octet 1 bits shall be encoded as follows:

八位字节1比特应编码如下：

- Bit 1 represents the SEID flag (T).

-位1代表SEID标志（T）。

- Bit 2 represents the "MP" flag (see clause 7.2.2.4.1).

-位2代表“ MP”标志（请参见第7.2.2.4.1节）。

- Bit 3 represents the "FO" flag (see clause 7.2.2.4.1).

-位3代表“ FO”标志（请参见第7.2.2.4.1节）。

- Bit 4 to 5 are spare, the sender shall set them to "0" and the receiving entity shall ignore them.

-位4至5是备用的，发送方应将它们设置为“ 0”，接收实体应忽略它们。

- Bits 6-8 represent the Version field.

-位6-8代表“版本”字段。

7.2.2.2 PFCP Header for Node Related Messages 节点相关消息的PFCP标头

The PFCP message header for the node related messages shall not contain the SEID field, but shall contain the Sequence Number field, followed by one spare octet as depicted in figure 7.2.2.2-1. The spare bits shall be set to zero by the sender and ignored by the receiver. For the Version Not Supported Response message, the Sequence Number may be set to any number and shall be ignored by the receiver.

节点相关消息的PFCP消息头不应包含SEID字段，但应包含Sequence Number字段，后跟一个备用八位字节，如图7.2.2.2-1所示。发送方应将备用位设置为零，接收方应忽略备用位。对于Version Not Supported Response报文，Sequence Number可以设置为任意数字，接收方可以忽略。

 

		Bits
Octets		8	7	6	5	4	3	2	1
1		Version			Spare	Spare	FO=0	MP=0	S=0
2		Message Type
3		Message Length (1st Octet) 邮件长度（第一个八位位组）
4		Message Length (2nd Octet) 邮件长度（第二个八位位组）
5		Sequence Number (1st Octet) 序列号（第一个八位位组）
6		Sequence Number (2nd Octet) 序列号（第二个八位位组）
7		Sequence Number (3rd Octet) 序列号（第三个八位位组）
8		Spare

Figure 7.2.2.2-1: PFCP Message Header for node related messages

图7.2.2.2-1：节点相关消息的PFCP消息头

7.2.2.3 PFCP Header for Session Related Messages 会话相关消息的PFCP标头

The PFCP message header, for session related messages, shall contain the SEID and Sequence Number fields followed by one spare octet. The PFCP header is depicted in figure 7.2.2.3-1. The spare bits shall be set to zero by the sender and ignored by the receiver.

会话相关消息的PFCP消息头应包含SEID和序列号字段，后跟一个备用八位字节。PFCP标头如图7.2.2.3-1所示。发送方应将备用位设置为零，接收方应忽略备用位。

 

		Bits
Octets		8	7	6	5	4	3	2	1
1		Version			Spare	Spare	FO	MP	S=1
2		Message Type
3		Message Length (1st Octet) 邮件长度（第一个八位位组）
4		Message Length (2nd Octet) 邮件长度（第二个八位位组）
5		Session Endpoint Identifier (1st Octet) 会话端点标识符（第一个八位位组）
6		Session Endpoint Identifier (2nd Octet) 会话端点标识符（第二个八位位组）
7		Session Endpoint Identifier (3rd Octet) 会话端点标识符（第三个八位位组）
8		Session Endpoint Identifier (4th Octet) 会话端点标识符（第四个八位位组）
9		Session Endpoint Identifier (5th Octet) 会话端点标识符（第五个八位位组）
10		Session Endpoint Identifier (6th Octet) 会话端点标识符（第六个八位位组）
11		Session Endpoint Identifier (7th Octet) 会话端点标识符（第7个八位位组）
12		Session Endpoint Identifier (8th Octet) 会话端点标识符（第8个八位位组）
13		Sequence Number (1st Octet) 序列号（第一个八位位组）
14		Sequence Number (2nd Octet) 序列号（第二个八位位组）
15		Sequence Number (3rd Octet) 序列号（第三个八位位组）
16		Message Priority				Spare

Figure 7.2.2.3-1: PFCP message Header for session related messages

图7.2.2.3-1：PFCP消息会话相关消息的标题

7.2.2.4 Usage of the PFCP Header PFCP标头的用法

7.2.2.4.1 General

The format of the PFCP header is specified in clause 7.2.2.

PFCP报头的格式在第7.2.2节中规定。

The usage of the PFCP header shall be as defined below.

PFCP报头的用法如下。

The first octet of the header shall be used is the following way:

报头的第一个八位字节应按以下方式使用：

- Bit 1 represents the "S" flag, which indicates if SEID field is present in the PFCP header or not. If the "S" flag is set to "0", then the SEID field shall not be present in the PFCP header. If the "S" flag is set to "1", then the SEID field shall immediately follow the Length field, in octets 5 to 12. Apart from the node related messages, in all PFCP messages the value of the "S" flag shall be set to "1".

-位1代表“ S”标志，该标志指示SEID字段是否存在于PFCP标头中。如果“ S”标志设置为“ 0”，则SEID字段不得出现在PFCP头中。如果“ S”标志设置为“ 1”，则SEID字段应紧随长度字段之后，以字节5至12为单位。除了与节点有关的消息外，在所有PFCP消息中，“ S”标志的值应为设置为“ 1”。

- Bit 2 represents the "MP" flag. If the "MP" flag is set to "1", then bits 8 to 5 of octet 16 shall indicate the message priority.

-位2代表“ MP”标志。如果“ MP”标志设置为“ 1”，则八位位组16的比特8至5将指示消息优先级。

- Bit 3 represents the "FO" (Follow On) flag. If the "FO" flag is set to "1", then another PFCP message follows in the UDP/IP packet (see clauses 6.5 and 7.2.1A).

-位3表示“ FO”（跟随打开）标志。如果将“ FO”标志设置为“ 1”，则在UDP / IP数据包中将跟随另一个PFCP消息（请参见第6.5和7.2.1A节）。

- Bit 4 is a spare bit. The sending entity shall set it to "0" and the receiving entity shall ignore it.

-位4是备用位。发送实体应将其设置为“ 0”，而接收实体应将其忽略。

- Bit 5 is a spare bit. The sending entity shall set it to "0" and the receiving entity shall ignore it.

-位5是备用位。发送实体应将其设置为“ 0”，而接收实体应将其忽略。

- Bits 6 to 8, which represent the PFCP version, shall be set to decimal 1 ("001").

-代表PFCP版本的第6至8位应设置为十进制1（“ 001”）。

The usage of the fields in octets 2 - n of the header shall be as specified below.

报头的八位字节2-n中字段的用法如下。

- Octet 2 represents the Message type field, which shall be set to the unique value for each type of control plane message. Message type values are specified in Table 7.3-1 "Message types".

-八位位组2代表消息类型字段，对于每种控制平面消息类型，该字段应设置为唯一值。消息类型值在表7.3-1“消息类型”中指定。

- Octets 3 to 4 represent the Message Length field. This field shall indicate the length of the message in octets excluding the mandatory part of the PFCP header (the first 4 octets). The SEID (if present) and the Sequence Number shall be included in the length count. The format of the Length field of information elements is specified in clause 8.2 "Information Element Format".

-八位字节3到4代表消息长度字段。该字段应指示消息的长度，以八位字节为单位，不包括PFCP头标的强制部分（前四个八位字节）。 SEID（如果存在）和序列号应包括在长度计数中。信息元素的长度字段的格式在第8.2节“信息元素格式”中指定。

- When S=1, Octets 5 to 12 represent the Session Endpoint Identifier (SEID) field. This field shall unambiguously identify a session endpoint in the receiving Packet Forward Control entity. The Session Endpoint Identifier is set by the sending entity in the PFCP header of all control plane messages to the SEID value provided by the corresponding receiving entity (CP or UP function). If a peer's SEID is not available the SEID field shall be present in a PFCP header, but its value shall be set to "0", "Conditions for sending SEID=0 in PFCP header".

-当S = 1时，字节5到12代表会话端点标识符（SEID）字段。该字段应明确标识接收分组转发控制实体中的会话端点。会话端点标识符由发送实体在所有控制平面消息的PFCP头中设置为相应接收实体（CP或UP功能）提供的SEID值。如果对等方的SEID不可用，则SEID字段应出现在PFCP头中，但其值应设置为“ 0”，“在PFCP头中发送SEID = 0的条件”。

NOTE: The SEID in the PFCP header of a message is set to the SEID value provided by the corresponding receiving entity regardless of whether the source IP address of the request message and the IP Destination Address provided by the receiving entity for subsequent request messages are the same or not.

注意：消息的PFCP标头中的SEID设置为相应接收实体提供的SEID值，而不管请求消息的源IP地址和接收实体为后续请求消息提供的IP目标地址是否是相同或不同。

- Octets 13 to 15 represent PFCP Sequence Number field.

-八位位组13到15代表PFCP序列号字段。

7.2.2.4.2 Conditions for Sending SEID=0 in PFCP Header 在PFCP标头中发送SEID = 0的条件

If a peer's SEID is not available, the SEID field shall still be present in the header and its value shall be set to "0" in the following messages:

如果对等方的SEID不可用，SEID字段仍应存在于报头中，并且其值应在以下消息中设置为“0”：

- PFCP Session Establishment Request message on Sxa/Sxb/Sxc;

-Sxa / Sxb / Sxc上的PFCP会话建立请求消息；

- If a node receives a message for which it has no session, i.e. if SEID in the PFCP header is not known, it shall respond with "Session context not found" cause in the corresponding response message to the sender, the SEID used in the PFCP header in the response message shall be then set to "0";

-如果节点接收到没有会话的消息，即如果PFCP头中的SEID未知，则它将在发送方的相应响应消息中以“未找到会话上下文”的原因进行响应，该节点使用然后，响应消息中的PFCP头应设置为“ 0”；

- If a node receives a request message containing protocol error, e.g. Mandatory IE missing, which requires the receiver to reject the message as specified in clause 7.6, it shall reject the request message. For the response message, the node should look up the remote peer's SEID and accordingly set SEID in the PFCP header and the message cause code. As an implementation option, the node may not look up the remote peer's SEID and set the PFCP header SEID to "0" in the response message. However in this case, the cause value shall not be set to "Session not found".

-如果节点收到包含协议错误的请求消息，例如强制性IE丢失，要求接收者按照第7.6节的规定拒绝消息，它将拒绝请求消息。对于响应消息，该节点应查找远程对等方的SEID，并相应地在PFCP标头和消息原因代码中设置SEID。作为一种实现方式，该节点可能不查找远程对等方的SEID，并且在响应消息中将PFCP标头SEID设置为“ 0”。但是，在这种情况下，原因值不得设置为“找不到会话”。