Tech-invite3GPPspaceIETF RFCsSIP
Quick21222324252627282931323334353637384‑5x

Content for  TS 24.501  Word version:  17.5.0

Top   Top   Up   Prev   Next
1…   3…   4…   4.4…   4.4.3…   4.5…   4.5.3…   4.6…   4.7…   4.9…   4.15…   5…   5.2…   5.3…   5.3.2…   5.3.7…   5.3.19…   5.4…   5.4.1.3…   5.4.2…   5.4.4…   5.4.5…   5.4.6…   5.5…   5.5.1.2.4   5.5.1.2.5…   5.5.1.3…   5.5.1.3.4   5.5.1.3.5…   5.5.2…   5.6…   5.6.2…   6…   6.1.4…   6.2…   6.3…   6.3.2…   6.3.3…   6.4…   6.4.1.4…   6.4.2…   6.5…   7…   8…   8.2.9…   8.3…   9…   9.11.2…   9.11.2.10…   9.11.3…   9.11.3.4…   9.11.3.8…   9.11.3.14…   9.11.3.18C…   9.11.3.29…   9.11.3.33…   9.11.3.39…   9.11.3.45…   9.11.3.50…   9.11.3.53A…   9.11.3.68…   9.11.3.75…   9.11.4…   9.11.4.10…   9.11.4.13…   9.11.4.16…   9.11.4.30…   9.12   10…   A…   B…   C…   D…   D.6…   D.6.3…

 

9.11.4.30  Requested MBS container |R17|Word‑p. 809

The purpose of the Requested MBS container information element is for UE to request to join or leave one or more MBS sessions.
The Requested MBS container information element is coded as shown in Figure 9.11.4.30.1, Figure 9.11.4.30.2, Figure 9.11.4.30.3, Figure 9.11.4.30.4 and Table 9.11.4.30.1.
The Requested MBS container is a type 4 information element with a minimum length of 7 octets and a maximum length of n octets.
Reproduction of 3GPP TS 24.501, Figure 9.11.4.30.1: Requested MBS container information element
Up
Reproduction of 3GPP TS 24.501, Figure 9.11.4.30.2: MBS session information
Up
Reproduction of 3GPP TS 24.501, Figure 9.11.4.30.3: MBS session ID for Type of MBS session ID =
Up
Reproduction of 3GPP TS 24.501, Figure 9.11.4.30.4: MBS session ID for Type of MBS session ID =
Up
This field contains the IP multicast address used as destination address in related IP packets for identifying a multicast service associated with the source.
The Destination IP address information is coded as the PDU address described in subclause 9.11.4.10 starting from octet 3 in Figure 9.11.4.10.1 and Table 9.11.4.10.1.
MBS operation (bits 1 to 2 of octet 3)
Bits
2 1
0 1Join MBS session
1 0Leave MBS session
All other values are reserved.
Bits 3 to 8 of octet 3 are spare and shall be coded as zero.
Type of MBS session ID (bits 1 to 2 of octet 4)
Bits
2 1
0 1Temporary Mobile Group Identity (TMGI)
1 0Source specific IP multicast address
All other values are reserved.
Bits 3 to 8 of octet 4 are spare and shall be coded as zero.
If Type of MBS session ID is set to "Temporary Mobile Group Identity (TMGI)", the MBS session ID contains the TMGI (octet 5 to i) and is coded as described in subclause 10.5.6.13 in TS 24.008 starting from octet 2.
If Type of MBS session ID is set to "Source specific IP multicast address", the MBS session ID contains the Source IP address information and the Destination IP address information.
Source IP address information (octet 5 to v)
This field contains the IP unicast address used as source address in IP packets for identifying the source of the multicast service.
The Source IP address information is coded as the PDU address described in subclause 9.11.4.10 starting from octet 3 in Figure 9.11.4.10.1 and Table 9.11.4.10.1.
Destination IP address information (octet v+1 to i)
Up

9.11.4.31  Received MBS container |R17|Word‑p. 811

The purpose of the Received MBS container information element is to indicate to the UE the information of the MBS sessions that the network accepts or rejects the UE to join, or the information of the MBS sessions that the UE is removed from.
The Received MBS container information element is coded as shown in Figure 9.11.4.31.1, Figure 9.11.4.31.2, Figure 9.11.4.31.3, Figure 9.11.4.31.4, Figure 9.11.4.31.5, Figure 9.11.4.31.6, Figure 9.11.4.31.7 and Table 9.11.4.31.1.
The Received MBS container is a type 4 information element with a minimum length of 6 octets and a maximum length of n octets.
Reproduction of 3GPP TS 24.501, Figure 9.11.4.31.1: Received MBS container information element
Up
Reproduction of 3GPP TS 24.501, Figure 9.11.4.31.2: Received MBS information
Up
Reproduction of 3GPP TS 24.501, Figure 9.11.4.31.3: MBS service area for MBS service area indication =
Up
Reproduction of 3GPP TS 24.501, Figure 9.11.4.31.4: MBS service area for MBS service area indication =
Up
Reproduction of 3GPP TS 24.501, Figure 9.11.4.31.5: MBS service area for MBS service area indication =
Up
Reproduction of 3GPP TS 24.501, Figure 9.11.4.31.6: NR CGI list
Up
Reproduction of 3GPP TS 24.501, Figure 9.11.4.31.7: NR CGI
Up
MBS decision (MD) (bits 1 and 2 of octet 3)
The MD indicates the network decision of the join requested by the UE or if the network requests to remove the UE from the MBS session.
Bits
2 1
0 1MBS join is accepted
1 0MBS join is rejected
1 1Remove UE from MBS session
All other values are reserved.
If MD is set to "MBS join is rejected", bits 5 to 8 of octet 3 shall contain the Rejection cause, otherwise bits 5 to 8 of octet 3 are spare and shall be coded as zero.
IP address existence (IPAE) (bit3 of octet 3)
The IPAE indicates whether the Source IP address information and Destination IP address information are included in the IE or not.
0Source and destination IP address information not included
1Source and destination IP address information included
Also If IPAE is set to "Source and destination IP address information included", Source IP address information and Destination IP address information shall be included in the IE, otherwise Source IP address information and Destination IP address information shall not be included in the IE.
MBS service area indication (MSAI) (bits 4 and 5 of octet 3)
The MSAI indicates whether the MBS service area is included in the IE or not
Bits
5 4
0 0MBS service area not included
0 1MBS service area included as MBS TAI list
1 0MBS service area included as NR CGI list
1 1MBS service area included as MBS TAI list and NR CGI list
Rejection cause (bits 6 to 8 of octet 3)
The Rejection cause indicates the reason of rejecting the join request.
Bits
8 7 6
0 0 0No additional information provided
0 0 1Insufficient resources
0 1 0User is not authorized to use MBS service
0 1 1MBS session has not started or will not start soon
1 0 0User is outside of local MBS service area
1 0 1Session context not found
All other values are unused in this version of the specification and interpreted as 000 if received.
TMGI (octets 4 to j)
The TMGI is coded as described in subclause 10.5.6.13 in TS 24.008 starting from octet 2.
Source IP address information (octet j+1 to v)
This field contains the IP unicast address used as source address in IP packets for identifying the source of the multicast service.
The Source IP address information is coded as the PDU address described in subclause 9.11.4.10 starting from octet 3 in Figure 9.11.4.10.1 and Table 9.11.4.10.1.
Destination IP address information (octet v+1 to k)
This field contains the IP multicast address used as destination address in related IP packets for identifying a multicast service associated with the source.
The Destination IP address information is coded as the PDU address described in subclause 9.11.4.10 starting from octet 3 in Figure 9.11.4.10.1 and Table 9.11.4.10.1.
MBS service area (octet k+1 to i)
The MBS service area contains either the MBS TAI list or the NR CGI list, that identify the service area(s) for a local MBS service.
MBS TAI list (octet k+1 to i)
The MBS TAI list is coded as the 5GS tracking area identity list defined in subclause 9.11.3.9.
NR CGI (octet k+1 to i)
The NR CGI globally identifies an NR cell. It contains the NR Cell ID and the PLMN ID of that cell.
NR Cell ID (octet k+1 to k+5)
The NR Cell ID consists of 36 bits identifying an NR Cell ID as specified in subclause 9.3.1.7 of TS 38.413, in hexadecimal representation. Bit 8 of octet y+1 is the most significant bit and bit 5 of octet y+5 is the least significant bit. Bits 1 to 4 of octet y+5 are spare and shall be coded as zero.
Up

9.11.4.32  PDU session pair ID |R17|Word‑p. 816

9.11.4.33  RSN |R17|Word‑p. 817


Up   Top   ToC