8.3.2.1 Message definition
The PDU SESSION ESTABLISHMENT ACCEPT message is sent by the SMF to the UE in response to PDU SESSION ESTABLISHMENT REQUEST message and indicates successful establishment of a PDU session. See table 8.3.2.1.1.
PDU SESSION ESTABLISHMENT ACCEPTメッセージは、PDU SESSION ESTABLISHMENT REQUESTメッセージに応答してSMFによってUEに送信され、PDUセッションの確立が成功したことを示します。表8.3.2.1.1を参照してください。
Message type: PDU SESSION ESTABLISHMENT ACCEPT
Extended protocol discriminator
PDU session ID
PTI
PDU SESSION ESTABLISHMENT ACCEPT message identity
Selected PDU session type
Selected SSC mode
Authorized QoS rules
Session AMBR ------Mandatory
Authorized QoS flow descriptions ---- Optional
9.11.4.12 QoS flow descriptions
~
Table 9.11.4.12.1: QoS flow descriptions information element
QoS flow identifier (QFI) (bits 6 to 1 of octet 4)
QFI field contains the QoS flow identifier.
Bits
6 5 4 3 2 1
0 0 0 0 0 0 no QoS flow identifier assigned
0 0 0 0 0 1 QFI 1★
to
1 1 1 1 1 1 QFI 63
The network shall not set the QFI value to 0.
Operation code (bits 8 to 6 of octet 5)
Bits
8 7 6
0 0 1 Create new QoS flow description★
0 1 0 Delete existing QoS flow description
0 1 1 Modify existing QoS flow description
All other values are reserved.
E bit (bit 7 of octet 6)
For the "create new QoS flow description" operation, the E bit is encoded as follows:
Bit
7
0 reserved
1 parameters list is included
For the "Delete existing QoS flow description" operation, the E bit is encoded as follows:
Bit
7
0 parameters list is not included
1 reserved
For the "modify existing QoS flow description" operation, the E bit is encoded as follows:
Bit
7
0 extension of previously provided parameters
1 replacement of all previously provided parameters
If the E bit is set to "parameters list is not included", the number of parameters field has zero value. If the E bit is set to "parameters list is included", the number of parameters field has non-zero value. If the E bit is set to "extension of previously provided parameters" or "replacement of all previously provided parameters", the number of parameters field has non-zero value. If the E bit is set to "extension of previously provided parameters" and one of the parameters in the new parameters list already exists in the previously provided parameters, the parameter shall be set to the new value.
Number of parameters (bits 6 to 1 of octet 6)
The number of parameters field contains the binary coding for the number of parameters in the parameters list field. The number of parameters field is encoded in bits 6 through 1 of octet 6 where bit 6 is the most significant and bit 1 is the least significant bit.
Parameters list (octets 7 to u)
The parameters list contains a variable number of parameters.
Each parameter included in the parameters list is of variable length and consists of:
- a parameter identifier (1 octet);
- the length of the parameter contents (1 octet); and
- the parameter contents itself (variable amount of octets).
The parameter identifier field is used to identify each parameter included in the parameters list and it contains the hexadecimal coding of the parameter identifier. Bit 8 of the parameter identifier field contains the most significant bit and bit 1 contains the least significant bit. In this version of the protocol, the following parameter identifiers are specified:
- 01H (5QI);
- 02H (GFBR uplink);★
- 03H (GFBR downlink);★
- 04H (MFBR uplink);
- 05H (MFBR downlink);
- 06H (Averaging window); and
- 07H (EPS bearer identity).
If the parameters list contains a parameter identifier that is not supported by the receiving entity the corresponding parameter shall be discarded.
The length of parameter contents field contains the binary coded representation of the length of the parameter contents field. The first bit in transmission order is the most significant bit.
When the parameter identifier indicates 5QI, the parameter contents field contains the binary representation of 5G QoS identifier (5QI) that is one octet in length.
5QI:★
Bits
8 7 6 5 4 3 2 1
0 0 0 0 0 0 0 0 Reserved
0 0 0 0 0 0 0 1 5QI 1
0 0 0 0 0 0 1 0 5QI 2
0 0 0 0 0 0 1 1 5QI 3
0 0 0 0 0 1 0 0 5QI 4
0 0 0 0 0 1 0 1 5QI 5
0 0 0 0 0 1 1 0 5QI 6
0 0 0 0 0 1 1 1 5QI 7
0 0 0 0 1 0 0 0 5QI 8
0 0 0 0 1 0 0 1 5QI 9
0 0 0 0 1 0 1 0
to Spare
0 1 0 0 0 0 0 0
0 1 0 0 0 0 0 1 5QI 65
0 1 0 0 0 0 1 0 5QI 66
0 1 0 0 0 0 1 1 5QI 67
0 1 0 0 0 1 0 0 Spare
0 1 0 0 0 1 0 1 5QI 69
0 1 0 0 0 1 1 0 5QI 70
0 1 0 0 0 1 1 1 5QI 71
0 1 0 0 1 0 0 0 5QI 72
0 1 0 0 1 0 0 1 5QI 73
0 1 0 0 1 0 1 0 5QI 74
0 1 0 0 1 0 1 1 5QI 75
0 1 0 0 1 1 0 0 5QI 76
0 1 0 0 1 1 0 1
to Spare
0 1 0 0 1 1 1 0
0 1 0 0 1 1 1 1 5QI 79
0 1 0 1 0 0 0 0 5QI 80
0 1 0 1 0 0 0 1 Spare
0 1 0 1 0 0 1 0 5QI 82
0 1 0 1 0 0 1 1 5QI 83
0 1 0 1 0 1 0 0 5QI 84
0 1 0 1 0 1 0 1 5QI 85
0 1 0 1 0 1 1 0 5QI 86
0 1 0 1 0 1 1 1
to Spare
0 1 1 1 1 1 1 1
1 0 0 0 0 0 0 0
to Operator-specific 5QIs
1 1 1 1 1 1 1 0
1 1 1 1 1 1 1 1 Reserved
The network shall consider all other values not explicitly defined in this version of the protocol as unsupported.
If the UE receives a 5QI value (excluding the reserved 5QI values) that it does not understand, the UE shall choose a 5QI value from the set of 5QI values defined in this version of the protocol (see 3GPP TS 23.501 [8]) and associated with:
- ★GBR QoS flows, if the QoS flow includes a GFBR uplink parameter, a GFBR downlink parameter, a MFBR uplink parameter and a MFBR downlink parameter; and
- non-GBR QoS flows, if the QoS flow does not include any one of a GFBR uplink parameter, a GFBR downlink parameter, a MFBR uplink parameter or a MFBR downlink parameter.
The UE shall use this chosen 5QI value for internal operations only. The UE shall use the received 5QI value in subsequent NAS signalling procedures.
When the parameter identifier indicates "★GFBR uplink", the parameter contents field contains one octet indicating the unit of the guaranteed flow bit rate for uplink followed by two octets containing the value of the guaranteed flow bit rate for uplink.
Unit of the guaranteed flow bit rate for uplink (octet 1)
Bits
8 7 6 5 4 3 2 1
0 0 0 0 0 0 0 0 value is not used (see NOTE 2)
0 0 0 0 0 0 0 1 value is incremented in multiples of 1 Kbps
0 0 0 0 0 0 1 0 value is incremented in multiples of 4 Kbps
0 0 0 0 0 0 1 1 value is incremented in multiples of 16 Kbps
0 0 0 0 0 1 0 0 value is incremented in multiples of 64 Kbps
0 0 0 0 0 1 0 1 value is incremented in multiples of 256 Kbps
0 0 0 0 0 1 1 0 value is incremented in multiples of 1 Mbps
0 0 0 0 0 1 1 1 value is incremented in multiples of 4 Mbps
0 0 0 0 1 0 0 0 value is incremented in multiples of 16 Mbps
0 0 0 0 1 0 0 1 value is incremented in multiples of 64 Mbps
0 0 0 0 1 0 1 0 value is incremented in multiples of 256 Mbps
0 0 0 0 1 0 1 1 value is incremented in multiples of 1 Gbps
0 0 0 0 1 1 0 0 value is incremented in multiples of 4 Gbps
0 0 0 0 1 1 0 1 value is incremented in multiples of 16 Gbps
0 0 0 0 1 1 1 0 value is incremented in multiples of 64 Gbps
0 0 0 0 1 1 1 1 value is incremented in multiples of 256 Gbps
0 0 0 1 0 0 0 0 value is incremented in multiples of 1 Tbps
0 0 0 1 0 0 0 1 value is incremented in multiples of 4 Tbps
0 0 0 1 0 0 1 0 value is incremented in multiples of 16 Tbps
0 0 0 1 0 0 1 1 value is incremented in multiples of 64 Tbps
0 0 0 1 0 1 0 0 value is incremented in multiples of 256 Tbps
0 0 0 1 0 1 0 1 value is incremented in multiples of 1 Pbps
0 0 0 1 0 1 1 0 value is incremented in multiples of 4 Pbps
0 0 0 1 0 1 1 1 value is incremented in multiples of 16 Pbps
0 0 0 1 1 0 0 0 value is incremented in multiples of 64 Pbps
0 0 0 1 1 0 0 1 value is incremented in multiples of 256 Pbps
Other values shall be interpreted as multiples of 256 Pbps in this version of the protocol.
Value of the guaranteed flow bit rate for uplink (octets 2 and 3)
Octets 2 and 3 represent the binary coded value of the guaranteed flow bit rate for uplink in units defined by the unit of the guaranteed flow bit rate for uplink.
When the parameter identifier indicates "GFBR downlink", the parameter contents field contains one octet indicating the unit of the guaranteed flow bit rate for downlink followed by two octets containing the value of the guaranteed flow bit rate for downlink.
Unit of the guaranteed flow bit rate for downlink (octet 1)
The coding is identical to that of the unit of the guaranteed flow bit rate for uplink.
Value of the guaranteed flow bit rate for downlink (octets 2 and 3)
Octets 2 and 3 represent the binary coded value of the guaranteed flow bit rate for downlink in units defined by the unit of the guaranteed flow bit rate for downlink.
When the parameter identifier indicates "MFBR uplink", the parameter contents field contains the one octet indicating the unit of the maximum flow bit rate for uplink followed by two octets containing the value of maximum flow bit rate for uplink.
Unit of the maximum flow bit rate for uplink (octet 1)
The coding is identical to that of the unit of the guaranteed flow bit rate for uplink.
Value of the maximum flow bit rate for uplink (octets 2 and 3)
Octets 2 and 3 represent the binary coded value of the maximum flow bit rate for uplink in units defined by the unit of the maximum flow bit rate for uplink.
When the parameter identifier indicates "MFBR downlink", the parameter contents field contains one octet indicating the unit of the maximum flow bit rate for downlink followed by two octets containing the value of the maximum flow bit rate for downlink.
Unit of the maximum flow bit rate for downlink (octet 1)
The coding is identical to that of the unit of the guaranteed flow bit rate for uplink.
Value of the maximum flow bit rate for downlink (octets 2 and 3)
Octets 2 and 3 represent the binary coded value of the maximum flow bit rate for downlink in units defined by the unit of the maximum flow bit rate for downlink.
In this version of the protocol, for messages specified in the present document, the sending entity shall not request 0 kbps for both the maximum flow bit rate for downlink and the maximum flow bit rate for uplink at the same time. Any entity receiving a request for 0 kbps in both the maximum flow bit rate for downlink and the maximum flow bit rate for uplink shall consider that as a syntactical error (see clause 7).
When the parameter identifier indicates "averaging window", the parameter contents field contains the binary representation of the averaging window for both uplink and downlink in milliseconds and the parameter contents field is two octets in length.
When the parameter identifier indicates EPS bearer identity, the length of EPS bearer identity is one octet, bits 5 to 8 of the parameter contents contain the EPS bearer identity as specified in subclause 9.3.2 of 3GPP TS 24.301 [15] (see NOTE) and bits 1 to 4 of the parameter contents are spare and shall be coded as zero. The UE shall not include the EPS bearer identity parameter in any mobile originated 5GSM messages.
Comentarios