3GPP 24.501 v20.0.0 — the document's own text
9.11.4.8 Mapped EPS bearer contexts
Taught in 4. Inside TS 24.501, the document at the centre (CT1 — the group that writes what your phone says, overview).
The purpose of the mapped EPS bearer contexts information element is to indicate a set of EPS bearer contexts for a PDU session, as described in clause 6.1.4.1.
The mapped EPS bearer contexts information element is a type 6 information element with a minimum length of 7 octet and a maximum length of 65538 octets.
The mapped EPS bearer contexts information element is coded as shown in figure 9.11.4.8.1, figure 9.11.4.8.2, figure 9.11.4.8.3 and table 9.11.4.8.1.
| 8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | ||
|---|---|---|---|---|---|---|---|---|---|
| Mapped EPS bearer contexts IEI | octet 1 | ||||||||
| Length of Mapped EPS bearer contexts contents | octet 2 | ||||||||
| octet 3 | |||||||||
| Mapped EPS bearer context 1 | octet 4octet u | ||||||||
| Mapped EPS bearer context 2 | octet u+1octet v | ||||||||
| … | octet v+1octet w | ||||||||
| Mapped EPS bearer context n | octet w+1octet x |
Figure 9.11.4.8.1: Mapped EPS bearer contexts
| 8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | ||
|---|---|---|---|---|---|---|---|---|---|
| EPS bearer identity | octet 4 | ||||||||
| Length of Mapped EPS bearer context | octet 5octet 6 | ||||||||
| Operation code | 0Spare | E bit | Number of EPS parameters | octet 7 | |||||
| EPS parameters list | octet 8*octet u* |
Figure 9.11.4.8.2: Mapped EPS bearer context
| 8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | ||
|---|---|---|---|---|---|---|---|---|---|
| EPS parameter identifier 1 | octet 8 | ||||||||
| Length of EPS parameter contents 1 | octet 9 | ||||||||
| EPS parameter contents 1 | octet 10octet h | ||||||||
| EPS parameter identifier 2 | octet h+1 | ||||||||
| Length of EPS parameter contents 2 | octet h+2 | ||||||||
| EPS parameter contents 2 | octet h+3octet i | ||||||||
| … | octet i+1octet j | ||||||||
| EPS parameter identifier N | octet j+1 | ||||||||
| Length of EPS parameter contents N | octet j+2 | ||||||||
| EPS parameter contents N | octet j+3octet u |
Figure 9.11.4.8.3: EPS parameters list
Table 9.11.4.8.1: Mapped EPS bearer contexts information element
| EPS bearer identity (octet 4)Bits 5 to 8 contain the EPS bearer identity, and are coded as specified in clause 9.3.2 of 3GPP TS 24.301 [15]. Bits 1 to 4 are spare and shall be coded as zero.Operation code (bits 8 to 7 of octet 7)Bits8 70 0 Reserved0 1 Create new EPS bearer1 0 Delete existing EPS bearer1 1 Modify existing EPS bearerBit 6 of octet 7 is spare and shall be coded as zero.E bit (bit 5 of octet 7)For the "create new EPS bearer" operation, the E bit is encoded as follows:Bit50 parameters list is not included (NOTE)1 parameters list is includedFor the "modify existing EPS bearer" operation, the E bit is encoded as follows:Bit50 extension of previously provided parameters list1 replacement of all previously provided parameters listIf the E bit is set to "parameters list is included", the number of EPS parameters field has non-zero value. If the E bit is set to "extension of previously provided parameters list" or "replacement of previously provided parameters list", 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. If the E bit is set to "replacement of all previously provided parameters list" and a parameter in the previously provided parameters is not provided in the new parameters list, the parameter shall be deleted.For the "create new EPS bearer" operation and "delete existing EPS bearer" operation, bit 5 of octet 7 is ignored.Number of EPS parameters (bits 4 to 1 of octet 7)The number of EPS parameters contains the binary coding for the number of EPS parameters in the EPS parameters list field. The number of EPS parameters field is encoded in bits 4 through 1 of octet 7 where bit 4 is the most significant and bit 1 is the least significant bit.EPS parameters list (octets 8 to u)The EPS parameters list contains a variable number of EPS parameters.Each EPS parameter included in the EPS parameters list is of variable length and consists of:- an EPS parameter identifier (1 octet); - the length of the EPS parameter contents (1 octet); and- the EPS parameter contents itself (variable amount of octets).The EPS parameter identifier field is used to identify each EPS parameter included in the EPS parameters list and it contains the hexadecimal coding of the EPS parameter identifier. Bit 8 of the EPS parameter identifier field contains the most significant bit and bit 1 contains the least significant bit. In this version of the protocol, the following EPS parameter identifiers are specified:- 01H (Mapped EPS QoS parameters);- 02H (Mapped extended EPS QoS parameters); and- 03H (Traffic flow template).- 04H (APN-AMBR).- 05H (extended APN-AMBR).If the EPS parameters list contains an EPS parameter identifier that is not supported by the receiving entity the corresponding EPS parameter shall be discarded.The length of EPS parameter contents field contains the binary coded representation of the length of the EPS parameter contents field. The first bit in transmission order is the most significant bit.When the parameter identifier indicates mapped EPS QoS parameters, the length and parameter contents field are coded as specified in clause 9.9.4.3 of 3GPP TS 24.301 [15].When the parameter identifier indicates mapped extended EPS QoS parameters, the length and parameter contents field are coded as specified in clause 9.9.4.30 of 3GPP TS 24.301 [15].When the parameter identifier indicates traffic flow template, the length and parameter contents field are coded from octet 2 as shown figure 10.5.144 and table 10.5.162 of 3GPP TS 24.008 [12].When the parameter identifier indicates APN-AMBR, the length and parameter contents field are coded as specified in clause 9.9.4.2 of 3GPP TS 24.301 [15].When the parameter identifier indicates Extended APN-AMBR, the length and parameter contents field are coded as specified in clause 9.9.4.29 of 3GPP TS 24.301 [15]. |
|---|
| NOTE: This value shall not be used In this version of the specification. |