Tech-invite  3GPPspace  IETFspace
21  22  23  24  25  26  27  28  29  31  32  33  34  35  36  37  38  4‑5x

Content for  TS 24.502  Word version:  19.0.0

Top   Top   Up   Prev   None
1…   4…   5…   5.3B…   6…   7…   7.2.5…   7.3…   7.3A…   7.4…   7.6…   7.9…   7.10…   8…   9…   9.3…   9.3.2…   9.3.2.2.3…   9.3.3… 
9.3.3 GRE encapsulated user data packet  9.4 NAS message envelope  $ Change history 

 

9.3.3  GRE encapsulated user data packet  p. 108

GRE encapsulated user data packet is coded according to Figure 9.3.3-1 and Table 9.3.3-1.
Reproduction of 3GPP TS 24.502, Fig. 9.3.3-1: GRE encapsulated user data packet
Figure 9.3.3-1: GRE encapsulated user data packet
Up
Octet 1 to octet 8 are the GRE header field defined in RFC 2784 and RFC 2890. The GRE header field is coded according to Figure 9.3.3-2 and Table 9.3.3-2.
Octet 9 to octet x are the Payload packet field. The Payload packet field contains one user data packet.
Reproduction of 3GPP TS 24.502, Fig. 9.3.3-2: GRE header field
Figure 9.3.3-2: GRE header field
Up
Bit 7 of octet 1 is the C bit defined in RFC 2784. The C bit is set to zero.
Bits 6, 3, 2, 1 and 0 of octet 1 and bits 7, 6, 5, 4, and 3 of octet 2 are the Reserved0 field defined in RFC 2784 and RFC 2890.
Bit 5 of octet 1 is the K bit defined in RFC 2890. The K bit is set to one.
Bit 4 of octet 1 is the S bit defined in RFC 2890. The S bit is set to zero.
Bits 2, 1 and 0 of octet 2 is the Ver field defined in RFC 2784.
Octet 3 and octet 4 are the Protocol Type field defined in RFC 2784. The Protocol Type field is set to zero. (see NOTE)
Octet 5 to octet 8 are the Key field defined in RFC 2890. The Key field is coded according to Figure 9.3.3-3 and Table 9.3.3-3.
NOTE:
The receiving entity shall ignore value of the Protocol Type field.
Reproduction of 3GPP TS 24.502, Fig. 9.3.3-3: Key field of GRE header
Figure 9.3.3-3: Key field of GRE header
Up
RQI (octet 8, bit 7)
0RQI is not indicated
1RQI is indicated
QFI (octet 5, bits 5 to 0)
Bits
5 4 3 2 1 0
0 0 0 0 0 0QFI 0
to
1 1 1 1 1 1QFI 63
Up

9.4  NAS message envelope  p. 109

NAS message envelope is used to frame the NAS message prior to its encapsulation as the TCP payload in the inner IP datagram.
NAS message envelope is encoded according to Figure 9.4-1 and Table 9.4-1.
Reproduction of 3GPP TS 24.502, Fig. 9.4-1: NAS message envelope format
Figure 9.4-1: NAS message envelope format
Up
Octet 1 and Octet 2 indicate the Length field. The Length field contains the length of the NAS message in bytes.
Octet 3 to octet m indicate the NAS Message field. The NAS Message field contains the NAS message which is to be framed in prior to encapsulation as the TCP payload in the inner IP datagram of the transmitted IP packet.
Up

$  Change history  p. 111

Up   Top