7.6 Test procedures for MBMS testing
34.1083GPPCommon test environments for User Equipment (UE)Conformance testingRelease 15TS
This clause specifies the procedures that shall be used for MBMS testing.
7.6.1 GMM-REGISTERED with 1 MBMS Service Activated
7.6.1.1 Initial conditions
User Equipment:
For MBMS broadcast test cases:
– The UE is in registered Idle Mode on PS state (state 3) if the UE only supports PS domain or registered Idle Mode on CS/PS (state 7) if the UE supports both CS and PS domain. The UE states are specified in clause 7.4.For MBMS multicast test cases:
– The UE is in CELL_DCH (6-10 PS-DCCH+DTCH_DCH) or CELL_FACH (6-11 PS-DCCH+DTCH_FACH) state after executing the procedure P13 or P14 defined in clause 7.4.2.6.
For MBMS broadcast and multicast test cases:
– Subsequent to the broadcasting of System Information, MCCH messages are transmitted by the SS using MBMS configuration C1 and Default1 MCCH scheduling (No ongoing service). See subclause 11.1.
– For MBMS the RRC messages used throughout the generic setup procedures make use of specific parameter settings as specified in clause 9.1.
7.6.1.2 Procedure
For MBMS broadcast test cases:
a) The SS request the UE to active the requested MBMS broadcast service.
b) The SS waits until the MBMS broadcast service has been activated in the UE
c) The SS change UE state to CELL_DCH (6-10 PS-DCCH+DTCH_DCH) or CELL_FACH (6-11 PS-DCCH+DTCH_FACH) state by executing the procedure P13 or P14 defined in clause 7.4.2.6 except for the reception of MBMS MODIFICATION REQUEST message after RRC CONNECTION SETUP COMPLETE message during P5 or P6 procedure in case of MBMS Selected Service.
Specific Message Content for MBMS MODIFICATION REQUEST:
MBMS MODIFICATION REQUEST
|
Information Element |
Value/remark |
|
MBMS preferred frequency request |
Check that the IE is not present |
|
MBMS RB list requested to be released |
Check that the IE is not present |
|
MBMS Selected Service Info |
|
|
– CHOICE Status |
Some |
|
– MBMS Selected Services Full |
|
|
– MBMS Selected Service ID |
|
|
– MBMS Service ID |
MBMS service ID of the activated MBMS service |
|
– CHOICE PLMN identity |
Check to see that one of the below choice element is present |
|
– SameAs-MIB |
(no data) |
|
– explicitPLMN_Id |
Check to see if it is set to the same value as "PLMN ID” in the Master Information block transmitted for the current serving cell. |
For MBMS multicast test cases:
|
Step |
Direction |
Message |
Comments |
|
|
UE |
SS |
|||
|
1 |
Make UE join a multicast service |
|||
|
2 |
|
IGMP/MLD JOIN |
IGMP/MLD |
|
|
3 |
|
request MBMS context activation |
SM |
|
|
4 |
|
Activate MBMS context request |
SM |
|
|
5 |
|
AUTHENTICATION AND CIPHERING REQUEST |
GMM |
|
|
6 |
|
AUTHENTICATION AND CIPHERING RESPONSE |
GMM |
|
|
7 |
|
Activate MBMS context Accept |
SM |
|
If required, transition from CELL_FACH (6-11) to CELL_PCH (6-12) or URA_PCH (6-13) state using the procedures P15 or P17 respectively will be performed.
7.6.1.3 Specific message contents
All specific message contents shall be referred to clause 9 with the following exceptions:
PHYSICAL CHANNEL RECONFIGURATION (procedures 6-12 and 6-13)
|
Information Element |
Value/remark |
|
UTRAN DRX cycle length coefficient |
7 |
Attach Accept message: GMM
|
Information Element |
Value/remark |
|
NetworkFeatureSupport |
MBMS supported |
Service Request message: GMM
|
Information Element |
Value/remark |
|
ServiceType |
MBMS Service Reception |
REQUEST MBMS CONTEXT ACTIVATION
|
Information Element |
Value/remark |
|
Linked NSAPI |
5 |
|
Offered Multicast address |
Present |
|
Access point name |
Present |
|
MBMS protocol configuration options |
Not present |
ACTIVATE MBMS CONTEXT REQUEST
|
Information Element |
Value/remark |
|
Requested MBMS NSAPI |
128 |
|
Requested LLC SAPI |
Present |
|
Supported MBMS bearer capabilities |
Present |
|
Requested Multicast address |
Present |
|
Access point name |
Present |
|
MBMS protocol configuration options |
Not present |
ACTIVATE MBMS CONTEXT ACCEPT
|
Information Element |
Value/remark |
|
Temporary Mobile Group Identity |
|
|
– MBMS Service Id |
Present |
|
– MCC |
Present |
|
– MNC |
Present |
|
Negotiated LLC SAPI |
Present |
|
MBMS protocol configuration options |
Not present |
IPv4_Datagram
|
Information Element |
Value/remark |
|
Version |
0x4 |
|
HeaderLength |
Present |
|
TypeOfService |
Present |
|
TotalLength |
Present |
|
Identification |
Present |
|
ReservedFlag |
Present |
|
MoreFragments |
Present |
|
FragmentationOffset |
Present |
|
TimeToLive |
Present |
|
Protocol |
Present |
|
HeaderCheckum |
Present |
|
SourceAddress |
Present |
|
DestinationAddress |
Present |
|
OptionsList |
Router alert option with value 0 (0x94040000) |
|
Data |
IGMP PDU |
IGMP/JOIN (IPv4)
|
Information Element |
Value/remark |
|
Type |
0x16 (Version 2 Membership Report) |
|
Max Resp Time |
Present |
|
Checksum |
Present |
|
Group Address |
Multicast IP address |
IGMP/Leave (IPv4)
|
Information Element |
Value/remark |
|
Type |
0x17 (Version 2 Membership Report) |
|
Max Resp Time |
Present |
|
Checksum |
Present |
|
Group Address |
Multicast IP address |
IPv6_Datagram
|
Information Element |
Value/remark |
|
Version |
0x6 |
|
TrafficClass |
Present |
|
FlowLabel |
Present |
|
PayloadLength |
Present |
|
NextHeader |
Present |
|
HopLimit |
Present |
|
SourceAddress |
Present |
|
DestinationAddress |
Present |
|
ExtensionHeaders |
Router alert option with value 0 (0x05020000) |
|
Data |
MLD PDU |
MLD/JOIN (IPv6)
|
Information Element |
Value/remark |
|
Type |
0x83 |
|
Code |
Present |
|
Checksum |
Present |
|
MaximumResponseDelay |
Present |
|
Reserved |
Present |
|
Group Address |
Multicast IP address |
MLD/LEAVE (IPv6)
|
Information Element |
Value/remark |
|
Type |
0x84 |
|
Code |
Present |
|
Checksum |
Present |
|
MaximumResponseDelay |
Present |
|
Reserved |
Present |
|
Group Address |
Multicast IP address |
7.6.2 IDLE with 1 MBMS Service Activated
7.6.2.1 Initial conditions
User Equipment:
For MBMS broadcast test cases:
– The UE is in registered Idle Mode on PS state (state 3) if the UE only supports PS domain or registered Idle Mode on CS/PS (state 7) if the UE supports both CS and PS domain. The UE states are specified in clause 7.4.
For MBMS multicast test cases:
– The UE is in CELL_FACH ( 6-11 PS-DCCH+DTCH_FACH) state after executing the procedure P14 defined in clause 7.4.2.6.
For MBMS broadcast and multicast test cases:
– Subsequent to the broadcasting of System Information, MCCH messages are transmitted by the SS using MBMS configuration C1 (No ongoing service) and Default1 MCCH scheduling. See subclause 11.1.
– For MBMS the RRC messages used throughout the generic setup procedures make use of specific parameter settings as specified in clause 9.1.
7.6.2.2 Procedure
For MBMS broadcast test cases:
a) The SS request the UE to active the requested MBMS broadcast service.
b) The SS waits until the MBMS broadcast service has been activated in the UE
For MBMS multicast test cases:
|
Step |
Direction |
Message |
Comments |
|
|
UE |
SS |
|||
|
1 |
Make UE join a multicast service |
|||
|
2 |
|
IGMP/MLD JOIN |
IGMP/MLD |
|
|
3 |
|
request MBMS context activation |
SM |
|
|
4 |
|
Activate MBMS context request |
SM |
|
|
5 |
|
AUTHENTICATION AND CIPHERING REQUEST |
GMM |
|
|
6 |
|
AUTHENTICATION AND CIPHERING RESPONSE |
GMM |
|
|
7 |
|
Activate MBMS context Accept |
SM |
|
|
8 |
|
RRC CONNECTION RELEASE |
RRC |
|
|
9 |
|
RRC CONNECTION RELEASE COMPLETE |
RRC |
|
7.6.2.3 Specific message contents
All specific message contents shall be referred to clause 9 with the following exceptions:
Attach Accept message: GMM
|
Information Element |
Value/remark |
|
NetworkFeatureSupport |
MBMS supported |
Service Request message: GMM
|
Information Element |
Value/remark |
|
ServiceType |
MBMS Service Reception |
REQUEST MBMS CONTEXT ACTIVATION
|
Information Element |
Value/remark |
|
Linked NSAPI |
5 |
|
Offered Multicast address |
Present |
|
Access point name |
Present |
|
MBMS protocol configuration options |
Not present |
ACTIVATE MBMS CONTEXT REQUEST
|
Information Element |
Value/remark |
|
Requested MBMS NSAPI |
128 |
|
Requested LLC SAPI |
Present |
|
Supported MBMS bearer capabilities |
Present |
|
Requested Multicast address |
Present |
|
Access point name |
Present |
|
MBMS protocol configuration options |
Not present |
ACTIVATE MBMS CONTEXT ACCEPT
|
Information Element |
Value/remark |
|
Temporary Mobile Group Identity |
|
|
– MBMS Service Id |
Present |
|
– MCC |
Present |
|
– MNC |
Present |
|
Negotiated LLC SAPI |
Present |
|
MBMS protocol configuration options |
Not present |
IPv4_Datagram
|
Information Element |
Value/remark |
|
Version |
0x4 |
|
HeaderLength |
Present |
|
TypeOfService |
Present |
|
TotalLength |
Present |
|
Identification |
Present |
|
ReservedFlag |
Present |
|
MoreFragments |
Present |
|
FragmentationOffset |
Present |
|
TimeToLive |
Present |
|
Protocol |
Present |
|
HeaderCheckum |
Present |
|
SourceAddress |
Present |
|
DestinationAddress |
Present |
|
OptionsList |
Router alert option with value 0 (0x94040000) |
|
Data |
IGMP PDU |
IGMP/JOIN (IPv4)
|
Information Element |
Value/remark |
|
Type |
0x16 (Version 2 Membership Report) |
|
Max Resp Time |
Present |
|
Checksum |
Present |
|
Group Address |
Multicast IP address |
IGMP/Leave (IPv4)
|
Information Element |
Value/remark |
|
Type |
0x17 (Version 2 Membership Report) |
|
Max Resp Time |
Present |
|
Checksum |
Present |
|
Group Address |
Multicast IP address |
IPv6_Datagram
|
Information Element |
Value/remark |
|
Version |
0x6 |
|
TrafficClass |
Present |
|
FlowLabel |
Present |
|
PayloadLength |
Present |
|
NextHeader |
Present |
|
HopLimit |
Present |
|
SourceAddress |
Present |
|
DestinationAddress |
Present |
|
ExtensionHeaders |
Router alert option with value 0 (0x05020000) |
|
Data |
MLD PDU |
MLD/JOIN (IPv6)
|
Information Element |
Value/remark |
|
Type |
0x83 |
|
Code |
Present |
|
Checksum |
Present |
|
MaximumResponseDelay |
Present |
|
Reserved |
Present |
|
Group Address |
Multicast IP address |
MLD/LEAVE (IPv6)
|
Information Element |
Value/remark |
|
Type |
0x84 |
|
Code |
Present |
|
Checksum |
Present |
|
MaximumResponseDelay |
Present |
|
Reserved |
Present |
|
Group Address |
Multicast IP address |
7.6.3 MBSFN IDLE
7.6.3.1 Initial conditions
System Simulator:
– 1 MBMS MBSFN Cell 31 with default parameters.
In addition to broadcasting System Information, MCCH messages are transmitted by the SS using MBMS configuration C1 and Default1 MCCH scheduling (No ongoing service). See subclause 11.1.
– 1 unicast carrier Cell 1 with default parameters.
User Equipment:
– The UE is in MBSFN Idle mode with one service activated on the MBSFN cell as specified in subclause 7.6.4.
– On the unicast carrier cell the UE is in registered Idle Mode on PS (state 3) if the UE only supports PS domain or registered Idle Mode on CS/PS (state 7) if the UE supports both CS and PS domains. See subclause 7.6.4. The UE states are specified in subclause 7.4.
7.6.3.2 Procedure
a) The SS requests the UE to de-activate the requested MBMS broadcast service.
b) The SS waits until the MBMS broadcast service has been de-activated in the UE
Expected Sequence:
|
Step |
Direction |
Carrier |
Message |
Comment |
|
|
UE |
SS |
||||
|
1 |
|
M |
SYSTEM INFORMATION (BCCH) |
||
|
2 |
|
M |
MBMS MCCH Message Configuration C1 |
MBMS configuration C1 and Default1 MCCH scheduling. No session ongoing. |
|
|
3 |
SS |
SS requests the UE to de-activate the required MBMS broadcast service |
|||
|
4 |
SS |
SS waits until the MBMS broadcast service has been de-activated in the UE. |
|||
7.6.3.3 Specific message contents
All message contents shall be as specified in clause 9.1.
7.6.4 MBSFN IDLE with 1 MBMS Service Activated
7.6.4.1 Initial conditions
System Simulator:
– 1 MBMS MBSFN Cell 31 with default parameters.
In addition to broadcasting System Information, MCCH messages are transmitted by the SS using MBMS configuration C2 and Default1 MCCH scheduling (No modified services. One ongoing service corresponding to that to be activated at the UE. 124 kbps PS RAB). See subclause 11.1.
– 1 unicast carrier Cell 1 with default parameters.
User Equipment:
– The UE is switched off.
– The Test-USIM shall be inserted.
– The UE shall be operated under normal test conditions.
7.6.4.2 Procedure
a) The UE shall be switched on and the unicast carrier mobile termination shall be activated.
b) The UE registers on the unicast carrier Cell 1. The UE registers on PS, as specified in clause 7.2.2.2 of TS 34.108 (state 3) if the UE only supports PS domain or registers on CS/PS, as specified in clause 7.2.2.3 of TS 34.108. (state 7) if the UE supports both CS and PS domains.
c) The SS sends ACTIVATE RB TEST MODE on the unicast carrier cell. The UE acknowledges by sending ACTIVATE RB TEST MODE COMPLETE.
d) The MBMS MBSFN mobile termination shall be activated. (See Note 1)
e) The SS sends CLOSE UE TEST LOOP via the unicast carrier cell, requesting activation of Test Loop Mode 3 specifying the MBSFN MBMS short transmission identity of the MTCH for the activated service (on Cell 31).
f) The SS requests the UE to activate the requested MBMS broadcast service.
g) The UE performs an MBSFN cell search, reads System Information and camps on Cell 31.
h) The UE reads the MCCH messages transmitted by the SS in accordance with Combination C2 and with Default1 MCCH information scheduling. See subclause 11.1. The UE shall continue acquiring the above MBMS messages until it has received a consistent set of MCCH information in the same modification period.
i) The UE shall establish the p-t-m radio bearer for the ongoing activated MBMS service indicated in the MBMS UNMODIFIED SERVICES INFORMATION message according to the configuration defined in the MBMS CURRENT CELL P-T-M INFORMATION (one ongoing session corresponding to the service activated at the UE. The UE closes the test loop and starts counting successfully received RLC PDUs on the MTCH. The UE will send CLOST UE TEST LOOP COMPLETE.
j) The Test Loop is opened and RB Test Mode is deactivated.
Expected Sequence:
|
Step |
Direction |
Carrier |
Message |
Comment |
|
|
UE |
SS |
||||
|
1 |
UE |
U |
UE switched on and unicast carrier mobile termination is activated. |
||
|
2 |
U |
UE registers on Unicast carrier Cell 1. |
|||
|
3 |
|
U |
ACTIVATE RB TEST MODE |
||
|
4 |
|
U |
ACTIVATE RB TEST MODE COMPLETE |
||
|
5 |
UE |
MBMS MBSFN mobile termination is activated. UE starts MBSFN cell search. Note 1. |
|||
|
6 |
|
U |
CLOSE UE TEST LOOP |
Loop back mode 3 on MTCH on Cell 31 is requested. |
|
|
7 |
SS |
SS requests the UE to activate the required MBMS broadcast service |
|||
|
8 |
|
M |
SYSTEM INFORMATION (BCCH) |
||
|
9 |
|
M |
MBMS MCCH Message Configuration C2 |
No modified services. One ongoing service corresponding to that activated at the UE. 124 kbps PS RAB |
|
|
10 |
UE |
M |
The UE shall continue acquiring the above MBMS messages until it has received a consistent set of MCCH information in the same modification period. |
||
|
11 |
|
M |
CLOSE UE TEST LOOP COMPLETE |
The UE shall establish the indicated p-t-m radio bearer and close the test loop. |
|
|
12 |
|
U |
OPEN UE TEST LOOP |
||
|
13 |
|
U |
OPEN UE TEST LOOP COMPLETE |
||
|
14 |
|
U |
DEACTIVATE RB TEST MODE |
||
|
15 |
|
U |
DEACTIVATE RB TEST MODE COMPLETE |
||
Note 1: If possible, activation of the MBMS Mobile Termination shall be delayed until registration on the unicast carrier is complete.
7.6.4.3 Specific message contents
All message contents shall be as specified in clause 9.1.