3GPP 24.501 v20.0.0 — the document's own text

9.11.4.14 Session-AMBR

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 Session-AMBR information element is to indicate the initial subscribed PDU session aggregate maximum bit rate when the UE establishes a PDU session or to indicate the new subscribed PDU session aggregate maximum bit rate if it is changed by the network.

The Session-AMBR information element is coded as shown in figure 9.11.4.14.1 and table 9.11.4.14.1.

The Session-AMBR is a type 4 information element with a length of 8 octets.

8	7	6	5	4	3	2	1
Session-AMBR IEI	octet 1
Length of Session-AMBR contents	octet 2
Unit for Session-AMBR for downlink	octet 3
Session-AMBR for downlink	octet 4-5
Unit for Session-AMBR for uplink	octet 6
Session-AMBR for uplink	octet 7-8

Figure 9.11.4.14.1: Session-AMBR information element

Table 9.11.4.14.1: Session-AMBR information element

Unit for Session-AMBR for downlink (octet 3)0 0 0 0 0 0 0 0 value is not used (see NOTE)0 0 0 0 0 0 0 1 value is incremented in multiples of 1 Kbps0 0 0 0 0 0 1 0 value is incremented in multiples of 4 Kbps0 0 0 0 0 0 1 1 value is incremented in multiples of 16 Kbps0 0 0 0 0 1 0 0 value is incremented in multiples of 64 Kbps0 0 0 0 0 1 0 1 value is incremented in multiples of 256 kbps0 0 0 0 0 1 1 0 value is incremented in multiples of 1 Mbps0 0 0 0 0 1 1 1 value is incremented in multiples of 4 Mbps0 0 0 0 1 0 0 0 value is incremented in multiples of 16 Mbps0 0 0 0 1 0 0 1 value is incremented in multiples of 64 Mbps0 0 0 0 1 0 1 0 value is incremented in multiples of 256 Mbps0 0 0 0 1 0 1 1 value is incremented in multiples of 1 Gbps0 0 0 0 1 1 0 0 value is incremented in multiples of 4 Gbps0 0 0 0 1 1 0 1 value is incremented in multiples of 16 Gbps0 0 0 0 1 1 1 0 value is incremented in multiples of 64 Gbps0 0 0 0 1 1 1 1 value is incremented in multiples of 256 Gbps0 0 0 1 0 0 0 0 value is incremented in multiples of 1 Tbps0 0 0 1 0 0 0 1 value is incremented in multiples of 4 Tbps0 0 0 1 0 0 1 0 value is incremented in multiples of 16 Tbps0 0 0 1 0 0 1 1 value is incremented in multiples of 64 Tbps0 0 0 1 0 1 0 0 value is incremented in multiples of 256 Tbps0 0 0 1 0 1 0 1 value is incremented in multiples of 1 Pbps0 0 0 1 0 1 1 0 value is incremented in multiples of 4 Pbps0 0 0 1 0 1 1 1 value is incremented in multiples of 16 Pbps0 0 0 1 1 0 0 0 value is incremented in multiples of 64 Pbps0 0 0 1 1 0 0 1 value is incremented in multiples of 256 PbpsOther values shall be interpreted as multiples of 256 Pbps in this version of the protocol.Session-AMBR for downlink (octets 4 and 5)Octets 4 and 5 represent the binary coded value of PDU session aggregated maximum bit rate for downlink in units defined by octet 3.Unit for Session-AMBR for uplink (octet 6)The coding is identical to the unit coding defined for Session-AMBR for downlink (octet 3)Session-AMBR for uplink (octets 7 and 8)Octets 7 and 8 represent the binary coded value of PDU session aggregated maximum bit rate for uplink in units defined by octet 6.
NOTE: In this release of the specifications if received it shall be interpreted as value is incremented in multiples of 1 Kbps. In earlier releases of specifications, the interpretation of this value is up to implementation.

Unit for Session-AMBR for downlink (octet 3)0 0 0 0 0 0 0 0 value is not used (see NOTE)0 0 0 0 0 0 0 1 value is incremented in multiples of 1 Kbps0 0 0 0 0 0 1 0 value is incremented in multiples of 4 Kbps0 0 0 0 0 0 1 1 value is incremented in multiples of 16 Kbps0 0 0 0 0 1 0 0 value is incremented in multiples of 64 Kbps0 0 0 0 0 1 0 1 value is incremented in multiples of 256 kbps0 0 0 0 0 1 1 0 value is incremented in multiples of 1 Mbps0 0 0 0 0 1 1 1 value is incremented in multiples of 4 Mbps0 0 0 0 1 0 0 0 value is incremented in multiples of 16 Mbps0 0 0 0 1 0 0 1 value is incremented in multiples of 64 Mbps0 0 0 0 1 0 1 0 value is incremented in multiples of 256 Mbps0 0 0 0 1 0 1 1 value is incremented in multiples of 1 Gbps0 0 0 0 1 1 0 0 value is incremented in multiples of 4 Gbps0 0 0 0 1 1 0 1 value is incremented in multiples of 16 Gbps0 0 0 0 1 1 1 0 value is incremented in multiples of 64 Gbps0 0 0 0 1 1 1 1 value is incremented in multiples of 256 Gbps0 0 0 1 0 0 0 0 value is incremented in multiples of 1 Tbps0 0 0 1 0 0 0 1 value is incremented in multiples of 4 Tbps0 0 0 1 0 0 1 0 value is incremented in multiples of 16 Tbps0 0 0 1 0 0 1 1 value is incremented in multiples of 64 Tbps0 0 0 1 0 1 0 0 value is incremented in multiples of 256 Tbps0 0 0 1 0 1 0 1 value is incremented in multiples of 1 Pbps0 0 0 1 0 1 1 0 value is incremented in multiples of 4 Pbps0 0 0 1 0 1 1 1 value is incremented in multiples of 16 Pbps0 0 0 1 1 0 0 0 value is incremented in multiples of 64 Pbps0 0 0 1 1 0 0 1 value is incremented in multiples of 256 PbpsOther values shall be interpreted as multiples of 256 Pbps in this version of the protocol.Session-AMBR for downlink (octets 4 and 5)Octets 4 and 5 represent the binary coded value of PDU session aggregated maximum bit rate for downlink in units defined by octet 3.Unit for Session-AMBR for uplink (octet 6)The coding is identical to the unit coding defined for Session-AMBR for downlink (octet 3)Session-AMBR for uplink (octets 7 and 8)Octets 7 and 8 represent the binary coded value of PDU session aggregated maximum bit rate for uplink in units defined by octet 6.

NOTE: In this release of the specifications if received it shall be interpreted as value is incremented in multiples of 1 Kbps. In earlier releases of specifications, the interpretation of this value is up to implementation.