6 UE pre-configuration MO parameters
24.5753GPP5G SystemMulticast/Broadcast UE pre-configuration Management Object (MO)Release 18TS
6.1 General
This clause describes the nodes and leaves of the UE pre-configuration MO parameters.
6.2 Node: <X>
This interior node acts as a placeholder for zero or one accounts for a fixed node.
– Occurrence: ZeroOrOne
– Format: node
– Access Types: Get
– Values: N/A
6.3 <X>/Name
The Name leaf is a name for the UE pre-configuration MO settings.
– Occurrence: ZeroOrOne
– Format: chr
– Access Types: Get
– Values: <User displayable name>
The User displayable name shall be represented by Unicode characters encoded as UTF-8 as specified in IETF RFC 3629 [7] and formatted using normalization form KC (NFKC) as specified in Unicode Standard Annex #15; Unicode Normalization Forms [9].
6.4 <X>/PLMNList
The PlmnList node acts as a placeholder for per-PLMN configuration.
– Occurrence: ZeroOrOne
– Format: node
– Access Types: Get, Replace
– Values: N/A
6.5 <X>/PLMNList/<X>/
This interior node acts as a placeholder for UE pre-configuration parameters for one PLMN.
– Occurrence: OneOrMore
– Format: node
– Access Types: Get, Replace
– Values: N/A
6.6 <X>/PLMNList/<X>/PLMNId
The PlmnId leaf indicates a PLMN identity of the PLMN for which the UE pre-configuration parameters applies.
– Occurrence: One
– Format: chr
– Access Types: Get, Replace
– Values: <PLMN identity>
The format of the PLMN identity is specified in 3GPP TS 23.003 [2].
6.7 <X>/PLMNList/<X>/TMGIConfiguration
The TMGIConfiguration node acts as a placeholder for the TMGI configuration in the PLMN identified by the PlmnId leaf.
– Occurrence: One
– Format: chr
– Access Types: Get, Replace
– Values: N/A
6.8 <X>/PLMNList/<X>/TMGIConfiguration/TMGIListForSA
The TMGIListForSA node acts as a placeholder for the TMGI list and the MBS service announcement information for broadcast communication services.
– Occurrence: ZeroOrOne
– Format: node
– Access Types: Get, Replace
– Values: N/A
6.9 <X>/PLMNList/<X>/TMGIConfiguration/TMGIListForSA/<X>
This node acts as a placeholder for one or more TMGI and the MBS service announcement information for broadcast communication service.
– Occurrence: OneOrMore
– Format: node
– Access Types: Get, Replace
– Values: N/A
6.10 <X>/PLMNList/<X>/TMGIConfiguration/TMGIListForSA/<X>/TMGI
The TMGI leaf indicates a TMGI for the MBS service announcement information for broadcast communication service.
– Occurrence: One
– Format: chr
– Access Types: Get, Replace
– Values: <TMGI>
The format of the TMGI is specified in 3GPP TS 23.003 [2].
6.11 <X>/PLMNList/<X>/TMGIConfiguration/TMGIListForSA/<X>/USD
The USD leaf provides MBS service announcement information for MBS service announcement service for broadcast communication service.
– Occurrence: ZeroOrOne
– Format: chr
– Access Types: Get, Replace
– Values: <USD>
The format of the USD is defined in 3GPP TS 26.346 [4].
6.12 <X>/PLMNList/<X>/TMGIConfiguration/TMGIListForService
The TMGIListForService node acts as a placeholder for the TMGI list and the MBS user service announcement information for the MBS user service for broadcast communication services.
– Occurrence: ZeroOrOne
– Format: node
– Access Types: Get, Replace
– Values: N/A
6.13 <X>/PLMNList/<X>/TMGIConfiguration/TMGIListForService/<X>
This node acts as a placeholder for one or more TMGI and MBS user service announcement information for the MBS user service for broadcast communication services.
– Occurrence: OneOrMore
– Format: node
– Access Types: Get, Replace
– Values: N/A
6.14 <X>/PLMNList/<X>/TMGIConfiguration/TMGIListForService/<X>/TMGI
The TMGI leaf indicates a TMGI for broadcast communication service.
– Occurrence: One
– Format: chr
– Access Types: Get, Replace
– Values: <TMGI>
The format of the TMGI is specified in 3GPP TS 23.003 [2].
6.15 <X>/PLMNList/<X>/TMGIConfiguration/TMGIListForService/<X>/USD
The USD leaf provides an USD for broadcast communication service using MBS. The USD leaf provides the MBS user service announcement information for the MBS user service corresponding to the broadcast communication service.
– Occurrence: ZeroOrOne
– Format: chr
– Access Types: Get, Replace
– Values: <USD>
The format of the USD is defined in 3GPP TS 26.346 [4].
6.16 <X>/PLMNList/<X>/RANInfo
The RANInfo node acts as a placeholder for the RAN-specific information.
– Occurrence: ZeroOrOne
– Format: chr
– Access Types: Get, Replace
– Values: N/A
6.17 <X>/PLMNList/<X>/RANInfo/<X>
This node acts as a placeholder for one or more NR ARFCN values of one or more MBS frequencies.
– Occurrence: OneOrMore
– Format: chr
– Access Types: Get, Replace
– Values: N/A
6.18 <X>/PLMNList/<X>/RANInfo/<X>/NRARFCN
The NRARFCN leaf indicates the NR-ARFCN value of one MBS frequency.
– Occurrence: One
– Format: int
– Access Types: Get, Replace
– Values: <NRARFCN>
The value of the NRARFCN is a 32-bit long unsigned integer. The format of the NR-ARFCN is specified in 3GPP TS 38.101-1 [5] and 3GPP TS 38.101-2 [6].
6.19 <X>/PLMNList/<X>/PDUInfo
The RANInfo node acts as a placeholder for the PDU session-specific information.
– Occurrence: ZeroOrOne
– Format: chr
– Access Types: Get, Replace
– Values: N/A
6.20 <X>/PLMNList/<X>/PDUInfo/PDUInfoList
The PDUInfoIList node acts as a placeholder for pairs of DNN and S-NSSAI values that indicate which PDU session is associated with an MBS session.
– Occurrence: ZeroOrOne
– Format: node
– Access Types: Get, Replace
– Values: N/A
6.21 <X>/PLMNList/<X>/PDUInfo/PDUInfoList/<X>
This node acts as a placeholder for one or more PDU session-specific information values.
– Occurrence: OneOrMore
– Format: chr
– Access Types: Get, Replace
– Values: N/A
6.22 <X>/PLMNList/<X>/PDUInfo/PDUInfoList/<X>/DNN
The DNN leaf indicates the DNN value of one PDU session associated with an MBS session.
– Occurrence: One
– Format: chr
– Access Types: Get, Replace
– Values: <DNN>
The format of the DNN is defined by 3GPP TS 23.003 [2] in clause 9A.
EXAMPLE: mycompany.mnc012.mcc340.gprs
6.23 <X>/PLMNList/<X>/PDUInfo/PDUInfoList/<X>/S-NSSAI
The S-NSSAI leaf indicates the S-NSSAI value of one PDU session associated with an MBS session.
– Occurrence: One
– Format: int
– Access Types: Get, Replace
– Values: <S-NSSAI>
The format of the S-NSSAI is defined by 3GPP TS 23.003 [2] in clause 28.4.2
Editor’s note: The need of a TMGI leaf for the DNN+S-NSSAI is for future study.
6.24 <X>/Ext
The Ext is an interior node for where the vendor specific information about the UE pre-configuration MO is being placed (vendor meaning application vendor, device vendor etc.). Usually the vendor extension is identified by vendor specific name under the ext node. The tree structure under the vendor identifier is not defined and can therefore include one or more non-standardized sub-trees.
– Occurrence: ZeroOrOne
– Format: node
– Access Types: Get
– Values: N/A
Annex A (informative):
Change history
|
Change history |
|||||||
|
Date |
Meeting |
TDoc |
CR |
Rev |
Cat |
Subject/Comment |
New version |
|
2022-04 |
CT1#135-e |
C1-223029 |
Draft skeleton provided by the rapporteur. |
0.0.0 |
|||
|
2022-04 |
CT1#135-e |
C1-223030 |
Implementing the following p-CR agreed by CT1: |
0.1.0 |
|||
|
2023-03 |
CT1#140 |
C1-230960 C1-230961 |
Implementing the following p-CRs agreed by CT1: editorials changes from the rapporteur. |
0.2.0 |
|||
|
2023-03 |
CT#99 |
CP-230183 |
TS presented for information and approval |
1.0.0 |
|||