4.9.34 Test procedure for MBS Multicast session join and session establishment
38.508-13GPP5GSPart 1: Common test environmentRelease 17TSUser Equipment (UE) conformance specification
4.9.34.1 Scope
The purpose of this procedure is to establish a multicast MBS session.
4.9.34.2 Procedure description
4.9.34.2.1 Initial conditions
System Simulator:
– 1 NR Cell connected to 5GC, default parameters.
User Equipment:
– The UE is in state 1N-A.
4.9.34.2.2 Procedure sequence
Table 4.9.34.2.2-1: Procedure for MBS Multicast session join and session establishment
St |
Procedure |
Message Sequence |
TP |
Verdict |
|
U – S |
Message/PDU/SDU |
||||
– |
EXCEPTION: Step 1a1 to 1b12a1 describe behaviour that depends on the UE capability the “lower case letter” identifies a step sequence that take place. |
– |
– |
– |
– |
1a1 |
IF pc_Join_MBS_by_PDU_Modification THEN cause the UE to request establishment of associated PDU Session to the MBS DNN.(Note 1) |
– |
– |
– |
– |
1a2-1a7 |
Steps 2-7 of expected sequence from Table 4.5.4.2-3 are performed. |
– |
– |
– |
– |
– |
EXCEPTION: Depending upon UE implementation, steps 1a8 and 1a9 can occur in any order |
– |
– |
– |
– |
1a8 |
The UE transmits an RRCReconfigurationComplete message. |
–> |
NR RRC: RRCReconfigurationComplete |
– |
– |
1a9 |
The UE transmits an UL NAS TRANSPORT message and a PDU SESSION ESTABLISHMENT REQUEST without MBS session ID and join request. |
–> |
NR RRC: ULInformationTransfer 5GMM: UL NAS TRANSPORT 5GSM: PDU SESSION ESTABLISHMENT REQUEST |
– |
P |
1a10 |
The SS transmits an RRCReconfiguration message and an PDU SESSION ESTABLISHMENT ACCEPT |
<– |
NR RRC: RRCReconfiguration 5GMM: DL NAS TRANSPORT 5GSM: PDU SESSION ESTABLISHMENT ACCEPT |
– |
– |
1a11 |
The UE transmits an RRCReconfigurationComplete message. |
–> |
NR RRC: RRCReconfigurationComplete |
– |
– |
– |
EXCEPTION: Step 1a12a1 describes behaviour depending UE implementation; the "lower case letter" identifies a step sequence that take place if the UE performs a specific action. |
– |
– |
– |
|
1a12a1 |
IF the ‘IP address allocation’ for the DNN for which the PDU session is established is set to "Yes" in Table 4.8.4-1 THEN, the generic procedure for IP address allocation in the user plane, specified in subclause 4.5A.3, takes place performing IP address allocation in the user plane. |
– |
– |
– |
– |
1a13 |
Trigger UE to join MBS Multicast session. |
– |
– |
– |
– |
1a14 |
The UE transmits an ULInformationTransfer message and a PDU SESSION MODIFICATION REQUEST message including MBS session ID and join request. |
–> |
NR RRC: ULInformationTransfer 5GMM: UL NAS TRANSPORT 5GSM: PDU SESSION MODIFICATION REQUEST |
– |
P |
1a15 |
The SS transmits an RRCReconfiguration message and a PDU SESSION MODIFICATION COMMAND. |
<– |
NR RRC: RRCReconfiguration 5GMM: DL NAS TRANSPORT 5GSM: PDU SESSION MODIFICATION COMMAND |
– |
– |
– |
EXCEPTION: Depending upon UE implementation, steps 1a16 and 1a17can occur in any order. |
– |
– |
– |
– |
1a16 |
The UE transmits an RRCReconfigurationComplete message. |
–> |
NR RRC: RRCReconfigurationComplete |
– |
– |
1a17 |
The UE transmits an ULInformationTransfer message and a PDU SESSION MODIFICATION COMPLETE message. |
–> |
NR RRC: ULInformationTransfer 5GMM: UL NAS TRANSPORT 5GSM: PDU SESSION MODIFICATION COMPLETE |
– |
P |
1b1 |
ELSE trigger UE to join MBS Multicast session. |
– |
– |
– |
– |
1b2-1b7 |
Steps 2-7 of expected sequence from Table 4.5.4.2-3 are performed. |
– |
– |
– |
– |
– |
EXCEPTION: Depending upon UE implementation, steps 1b8 and 1b9 can occur in any order |
– |
– |
– |
– |
1b8 |
The UE transmits an RRCReconfigurationComplete message. |
–> |
NR RRC: RRCReconfigurationComplete |
– |
– |
1b9 |
The UE transmits an UL NAS TRANSPORT message and a PDU SESSION ESTABLISHMENT REQUEST including MBS session ID and join request. |
–> |
NR RRC: ULInformationTransfer 5GMM: UL NAS TRANSPORT 5GSM: PDU SESSION ESTABLISHMENT REQUEST |
– |
P |
1b10 |
The SS transmits an RRCReconfiguration message and a PDU SESSION ESTABLISHMENT ACCEPT |
<– |
NR RRC: RRCReconfiguration 5GMM: DL NAS TRANSPORT 5GSM: PDU SESSION ESTABLISHMENT ACCEPT |
– |
– |
1b11 |
The UE transmits an RRCReconfigurationComplete message. |
–> |
NR RRC: RRCReconfigurationComplete |
– |
– |
– |
EXCEPTION: Step 1b12a1 describes behaviour depending UE implementation; the "lower case letter" identifies a step sequence that take place if the UE performs a specific action. |
– |
– |
– |
– |
1b12a1 |
IF the ‘IP address allocation’ for the DNN for which the PDU session is established is set to "Yes" in Table 4.8.4-1 THEN, the generic procedure for IP address allocation in the user plane, specified in subclause 4.5A.3, takes place performing IP address allocation in the user plane. |
– |
– |
– |
– |
Note 1: This could be done by e.g. MMI or AT command. |
4.9.34.3 Specific message contents
Table 4.9.34.3-1: PDU SESSION ESTABLISHMENT REQUEST (step 1a9, Table 4.9.34.2.2-1)
Derivation Path: Table 4.7.2-1. |
||||
Information Element |
Value/remark |
Comment |
Condition |
|
Requested MBS container |
Not present |
Table 4.9.34.3-2: PDU SESSION MODIFICATION REQUEST (step 1a14, Table 4.9.34.2.2-1)
Derivation Path: Table 4.7.2-7. |
||||
Information Element |
Value/remark |
Comment |
Condition |
|
Requested MBS container |
||||
MBS session information |
||||
MBS operation |
‘01’B |
Join MBS session |
||
Type of MBS session ID |
Not checked |
|||
MBS session ID |
Present but value not checked, the value is set according to the parameter given in the test case |
Table 4.9.34.3-3: PDU SESSION MODIFICATION COMMAND (step 1a15, Table 4.9.34.2.2-1)
Derivation Path: Table 4.7.2-9. |
||||
Information Element |
Value/remark |
Comment |
Condition |
|
Received MBS container |
||||
Received MBS information |
||||
Rejection cause |
‘000’B |
No additional information provided |
||
MSAI |
‘00’B |
MBS service area not included |
||
MD |
‘010’B |
MBS join is accepted |
||
MSCI |
‘0’B |
MBS security container not included |
||
MTI |
‘00’B |
No MBS timers included |
||
IPAE |
‘0’B |
Source and destination IP address information not included |
||
TMGI |
||||
MBMS Service ID |
‘000001’B |
|||
MCC |
See table 4.4.2-3 |
|||
MNC |
See table 4.4.2-3 |
|||
Source IP address information |
Not present |
|||
Destination IP address information |
Not present |
|||
MBS service area |
Not present |
|||
MBS timers |
Not present |
|||
MBS security container |
Not present |
Table 4.9.34.3-4: PDU SESSION ESTABLISHMENT REQUEST (step 1b9, Table 4.9.34.2.2-1)
Derivation Path: Table 4.7.2-1. |
||||
Information Element |
Value/remark |
Comment |
Condition |
|
Requested MBS container |
||||
MBS session information |
||||
MBS operation |
‘01’B |
Join MBS session |
||
Type of MBS session ID |
Not checked |
|||
MBS session ID |
Present but value not checked, the value is set according to the parameter given in the test case. |
Table 4.9.34.3-5: PDU SESSION ESTABLISHMENT ACCEPT (step 1b10, Table 4.9.34.2.2-1)
Derivation Path: Table 4.7.2-2. |
||||
Information Element |
Value/remark |
Comment |
Condition |
|
Received MBS container |
||||
Received MBS information |
||||
Rejection cause |
‘000’B |
No additional information provided |
||
MSAI |
‘00’B |
MBS service area not included |
||
MD |
‘010’B |
MBS join is accepted |
||
MSCI |
‘0’B |
MBS security container not included |
||
MTI |
‘00’B |
No MBS timers included |
||
IPAE |
‘0’B |
Source and destination IP address information not included |
||
TMGI |
||||
MBMS Service ID |
‘000001’B |
|||
MCC |
See table 4.4.2-3 |
|||
MNC |
See table 4.4.2-3 |
|||
Source IP address information |
Not present |
|||
Destination IP address information |
Not present |
|||
MBS service area |
Not present |
|||
MBS timers |
Not present |
|||
MBS security container |
Not present |