8.48 Fully Qualified Container (F-Container)
29.2743GPP3GPP Evolved Packet System (EPS)Evolved General Packet Radio Service (GPRS) Tunnelling Protocol for Control plane (GTPv2-C)Release 18Stage 3TS
Fully Qualified Container (F-Container) is coded as depicted in Figure 8.48-1.
All Spare bits are set to zeros by the sender and ignored by the receiver.
|
Bits |
||||||||||
|
Octets |
8 |
7 |
6 |
5 |
4 |
3 |
2 |
1 |
||
|
1 |
Type = 118 (decimal) |
|||||||||
|
2 to 3 |
Length = n |
|||||||||
|
4 |
Spare |
Instance |
||||||||
|
5 |
Spare |
Container Type |
||||||||
|
6 to (n+4) |
F-Container field |
|||||||||
Figure 8.48-1: Full Qualified Container (F-Container)
The F-Container field shall contain one of the following information, depending of the contents of the container transported by the specific GTP Information Element:
– transparent copy of the corresponding IEs (see clause 8.2.2):
– the "Source to Target Transparent Container" or the "Target to Source Transparent Container" as specified in 3GPP TS 25.413 [33]; or
– the "SON Configuration Transfer" as specified in 3GPP TS 36.413 [10] or "EN-DC SON Configuration Transfer" as specified in 3GPP TS 36.413 [10]; or
– the "Inter-system SON Configuration Transfer" as specified in 3GPP TS 36.413 [10] and 3GPP TS 38.413 [84]; or
– the "eNB Status Transfer Transparent Container" or eNB Early Status Transfer Transparent Container as specified in 3GPP TS 36.413 [10]; or
– "Source BSS to Target BSS Transparent Container" or "Target BSS to Source BSS Transparent Container" as specified in 3GPP TS 48.018 [34] or 3GPP TS 25.413 [33], which contains the value part of the "Source BSS to Target BSS Transparent Container" IE or the value part of the "Target BSS to Source BSS Transparent Container" IE defined in 3GPP TS 48.018 [34], i.e. octets 3 to n, excluding octet 1 (Element ID) and octet 2, 2a (Length); or
– transparent copy of the value part of the "NBIFOM Container" as specified in 3GPP TS 24.161 73].
– transparent copy of the octets of the encoded OCTET STRING of the "Source to Target Transparent Container" or the "Target to Source Transparent Container" specified in 3GPP TS 36.413 [10] and 3GPP TS 38.413 [84]; or
– transparent copy of the BSSGP RIM PDU as specified in 3GPP TS 48.018 [34]; or
– the Packet Flow ID, Radio Priority, SAPI, PS Handover XID parameters as specified in figure 8.42-2.
NOTE 1: Annex B.2 provides further details on the encoding of Generic Transparent Containers over RANAP, S1-AP and GTP. See also Annex C of 3GPP TS 36.413 [10] for further details on how the MME constructs the F-Container field from the Source to Target Transparent Container or Target to Source Transparent Container IEs received from S1-AP.
Container Type values are specified in Table 8.48-2.
Table 8. 48-2: Container Type values
|
Container Types |
Values (Decimal) |
|
Reserved |
0 |
|
UTRAN Transparent Container |
1 |
|
BSS Container |
2 |
|
E-UTRAN Transparent Container |
3 |
|
NBIFOM Container |
4 |
|
EN-DC Container |
5 |
|
Inter-System SON Container |
6 |
|
<spare> |
7-255 |
NOTE 2: For any other new future F-Container content types, new Container Type values may be needed, although use of RAT agnostic containers should be used whenever possible.
The BSS Container IE in the Bearer Context IE in Forward Relocation Request and Context Response messages is coded as depicted in Figure 8.48-3.
|
Bits |
||||||||||
|
Octets |
8 |
7 |
6 |
5 |
4 |
3 |
2 |
1 |
||
|
6 |
Spare |
PHX |
SAPI |
RP |
PFI |
|||||
|
a |
Packet Flow ID |
|||||||||
|
b |
SAPI |
Spare |
Radio Priority |
|||||||
|
c |
XiD parameters length |
|||||||||
|
d to n |
XiD parameters |
|||||||||
Figure 8.48-3: BSS Container
The flags PFI, RP, SAPI and PHX in octet 6 indicate the corresponding type of parameter (Packet FlowID, Radio Priority, SAPI and PS handover XID parameters) shall be present in a respective field or not. If one of these flags is set to "0", the corresponding field shall not be present at all. The Spare bit shall be set to zero by the sender and ignored by the receiver.
If PFI flag is set, Packet Flow ID shall be present in Octet a.
If RP flag is set, Radio Priority shall be present in Octet b.
If SAPI flag is set, SAPI shall be present in Octet b.
If PHX flag is set:
– XiD parameters length is present in Octet c.
– XiD parameters are present in Octet d to n.