Tech-invite  3GPPspace  IETFspace
◀  ▶  21  22  23  24  25  26  27  28  29  31  32  33  34  35  36  37  38  4‑5x
back to TS 23.280

Table of Contents for  TS 23.280  Word version:  20.1.0

1Scope  p. 19
2References  p. 19
3Definitions, symbols and abbreviations  p. 21
3.1Definitions  p. 21
3.2Symbols  p. 24
3.3Abbreviations  p. 24
4Introduction  p. 25
5Assumptions and architectural requirements  p. 26
5.1Assumptions  p. 26
5.1.1Service continuity  p. 26
5.1.2Trust domain  p. 26
5.2Architectural requirements  p. 26
5.2.1General architectural requirements  p. 26
5.2.2PLMN change requirements  p. 27
5.2.3UE-to-network relay MC service requirements  p. 27
5.2.4MC service user profile requirements  p. 27
5.2.4aRecording admin and/or replay service user profile requirements |R19|  p. 27
5.2.5MC service group affiliation and MC service group de-affiliation  p. 28
5.2.6GCS AS requirements for the MC services  p. 28
5.2.7Bearer management  p. 29
5.2.7.0General  p. 29
5.2.7.1MBMS bearer management  p. 30
5.2.7.2EPS bearer considerations  p. 30
5.2.7.2.1Considerations for the EPS bearer to the MC services PDN  p. 30
5.2.7.2.2Considerations for the EPS bearer to the MC common core services PDN and MC identity management service PDN  p. 30
5.2.8External applications access to services in a MC system  p. 30
5.2.9Migration |R15|  p. 31
5.2.9.1General  p. 31
5.2.9.2PLMN utilisation  p. 31
5.2.9.3SIP core / IMS utilisation  p. 32
5.2.10Interconnection |R15|  p. 32
5.2.10.1General  p. 32
5.2.10.2Connectivity  p. 32
5.2.10.3Migration  p. 33
5.2.10.4Private calls  p. 33
5.2.10.5Group calls  p. 33
5.2.10.6Group configuration  p. 33
5.2.10.7MC system topology hiding  p. 33
5.2.11Use of priorities |R17|  p. 33
5.2.11.1Requested priority  p. 33
5.2.12Recording and replay requirements |R19|  p. 33
5.2.13MC gateway UE requirements |R19|  p. 34
5.2.14Sharing administrative configuration between interconnected MC systems requirements |R19|  p. 34
6Involved business relationships  p. 34
7Functional model  p. 37
7.1General  p. 37
7.2Description of the planes  p. 37
7.3Functional model description  p. 37
7.3.1On-network functional model  p. 37
7.3.1.1General |R19|  p. 37
7.3.1.2Functional model for an MC system |R19|  p. 37
7.3.1.3Functional model for Recording admin UE and Replay UE |R19|  p. 41
7.3.2Off-network functional model  p. 42
7.4Functional entities description  p. 43
7.4.1General  p. 43
7.4.2Application plane  p. 43
7.4.2.1General  p. 43
7.4.2.2Common services core  p. 43
7.4.2.2.1Configuration management client  p. 43
7.4.2.2.2Configuration management server (CMS)  p. 44
7.4.2.2.3Group management client  p. 44
7.4.2.2.4Group management server (GMS)  p. 44
7.4.2.2.5Identity management client  p. 44
7.4.2.2.6Identity management server (IdMS)  p. 44
7.4.2.2.7Key management client  p. 44
7.4.2.2.8Key management server (KMS)  p. 44
7.4.2.2.9Location management client  p. 45
7.4.2.2.10Location management server (LMS)  p. 45
7.4.2.2.11Void  p. …
7.4.2.2.12Functional alias management client |R15|  p. 45
7.4.2.2.13Functional alias management server |R15|  p. 45
7.4.2.2.14Void  p. …
7.4.2.2.15Void  p. …
7.4.2.3MC service  p. 45
7.4.2.3.1MC service client  p. 45
7.4.2.3.2MC service server  p. 45
7.4.2.3.3MC service user database  p. 46
7.4.2.3.4MC gateway server |R15|  p. 46
7.4.2.4Recording and replay |R19|  p. 46
7.4.2.4.1Replay client  p. 46
7.4.2.4.2Recording server  p. 46
7.4.2.4.3Mass storage  p. 46
7.4.2.4.4Recording admin client  p. 46
7.4.2.5Administrative Configuration Management |R19|  p. 47
7.4.2.5.1ACM client  p. 47
7.4.2.5.2ACM server  p. 47
7.4.3Signalling control plane  p. 47
7.4.3.1SIP entities  p. 47
7.4.3.1.1Signalling user agent  p. 47
7.4.3.1.2SIP AS  p. 47
7.4.3.1.3SIP core  p. 47
7.4.3.1.3.1General  p. 47
7.4.3.1.3.2Local inbound / outbound proxy  p. 48
7.4.3.1.3.3Registrar finder  p. 48
7.4.3.1.3.4Registrar / application service selection  p. 48
7.4.3.1.4Diameter proxy |R15|  p. 49
7.4.3.2SIP database  p. 49
7.4.3.2.1General  p. 49
7.4.3.2.2SIP database logical functions  p. 50
7.4.3.3HTTP entities  p. 50
7.4.3.3.1HTTP client  p. 50
7.4.3.3.2HTTP proxy  p. 50
7.4.3.3.3HTTP server  p. 51
7.5Reference points  p. 51
7.5.1General reference point principle  p. 51
7.5.2Application plane  p. 51
7.5.2.1General  p. 51
7.5.2.2Reference point CSC-1 (between the identity management client and the identity management server)  p. 51
7.5.2.3Reference point CSC-2 (between the group management client and the group management server for configuration while UE is on-network)  p. 51
7.5.2.4Reference point CSC-3 (between the MC service server and the group management server)  p. 51
7.5.2.5Reference point CSC-4 (between the configuration management client and the configuration management server for configuration while UE is on-network)  p. 52
7.5.2.6Reference point CSC-5 (between the MC service server and the configuration management server)  p. 52
7.5.2.7Reference point CSC-7 (between the group management servers)  p. 52
7.5.2.8Reference point CSC-8 (between the key management server and the key management client)  p. 52
7.5.2.9Reference point CSC-9 (between the key management server and the MC service server)  p. 52
7.5.2.10Reference point CSC-10 (between the key management server and the group management server)  p. 53
7.5.2.11Reference point CSC-11 (between the configuration management client and the configuration management server for configuration while UE is off-network)  p. 53
7.5.2.12Reference point CSC-12 (between the group management client and the group management server for configuration while UE is off-network)  p. 53
7.5.2.13Reference point CSC-13 (between the configuration management server and the MC service user database)  p. 53
7.5.2.14Reference point CSC-14 (between the location management client and the location management server)  p. 53
7.5.2.15Reference point CSC-15 (between the location management server and the MC service server)  p. 53
7.5.2.16Reference point CSC-16 (between group management servers in different MC systems) |R15|  p. 54
7.5.2.17Reference point CSC-17 (between configuration management servers in different MC systems) |R15|  p. 54
7.5.2.18Void  p. …
7.5.2.19Reference point MCX-1 (between MC service servers) |R15|  p. 54
7.5.2.20Reference point CSC-19 (between group management server and MC gateway server) |R16|  p. 54
7.5.2.21Reference point CSC-20 (between configuration management server and MC gateway server) |R16|  p. 55
7.5.2.22Reference point CSC-21 (between MC gateway servers in different MC systems) |R16|  p. 55
7.5.2.23Reference point CSC-22 (between location management servers in different MC systems) |R18|  p. 55
7.5.2.24Reference point CSC-23 (between location management server and MC gateway server) |R18|  p. 55
7.5.2.25Reference point CSC-24 (between the Location management server and the configuration management server) |R18|  p. 55
7.5.2.25aReference point CSC-25 (between the group management server and the configuration management server) |R19|  p. 55
7.5.2.26Reference point ACM-1 (between administrative configuration management client and administrative configuration management server) |R19|  p. 56
7.5.2.27Reference point ACM-2 (between ACM server of primary MC system and ACM server of partner MC system) |R19|  p. 56
7.5.2.28Reference point ACM-3 (between ACM server and MC gateway server) |R19|  p. 56
7.5.2.29Reference point REC-1 (between the replay client and the recording server) |R19|  p. 56
7.5.2.30Void  p. …
7.5.2.31Reference point REC-2 (between recording server and key management server) |R19|  p. 57
7.5.2.32Reference point REC-3 (between recording server and configuration management server) |R19|  p. 57
7.5.2.33Void  p. …
7.5.2.34Reference point REC-4 (between recording server and MC service servers) |R19|  p. 57
7.5.2.35Void  p. …
7.5.2.36Reference point Le |R19|  p. 57
7.5.2.37Reference point REC-5 (between recording server and group management server) |R19|  p. 57
7.5.3Signalling control plane  p. 58
7.5.3.1General  p. 58
7.5.3.2Reference point SIP-1(between the signalling user agent and the SIP core)  p. 58
7.5.3.3Reference point SIP-2 (between the SIP core and the SIP AS)  p. 58
7.5.3.4Reference point SIP-3 (between the SIP core and SIP core)  p. 58
7.5.3.5Reference point HTTP-1 (between the HTTP client and the HTTP proxy)  p. 59
7.5.3.6Reference point HTTP-2 (between the HTTP proxy and the HTTP server)  p. 59
7.5.3.7Reference point HTTP-3 (between the HTTP proxy and HTTP proxy)  p. 59
7.5.3.8Reference point AAA-1 (between the SIP database and the SIP core)  p. 59
7.5.3.9Reference point AAA-2 (between the SIP core and Diameter proxy) |R15|  p. 59
8Identities  p. 59
8.1Application plane  p. 59
8.1.1Mission Critical user identity (MC ID)  p. 59
8.1.2MC service user identity (MC service ID)  p. 59
8.1.2aRecording admin and replay service user identity (MCRec ID) |R19|  p. 60
8.1.3MC service group identity (MC service group ID)  p. 60
8.1.3.1General  p. 60
8.1.3.2MC service group ID management (off-network operation)  p. 61
8.1.4MC system identity (MC system ID) |R15|  p. 61
8.1.5Functional Alias |R16|  p. 61
8.1.6MC service UE label |R17|  p. 62
8.1.7Void  p. …
8.2SIP signalling control plane  p. 62
8.3Relationship between identities in different planes  p. 63
8.3.1Relationship between MC service ID and public user identity  p. 63
8.3.2Relationship between MC service group ID and public service identity  p. 63
9Application of functional model to deployments  p. 64
9.1General  p. 64
9.2Architecture model and deployment scenarios for on-network operations  p. 64
9.2.1On-network architectural model  p. 64
9.2.1.1On-network architectural model diagram  p. 64
9.2.1.2Application services layer  p. 65
9.2.1.2.1Overview  p. 65
9.2.1.2.2Common services core  p. 65
9.2.1.2.3MC services  p. 65
9.2.1.3SIP core  p. 65
9.2.1.4EPS  p. 65
9.2.1.5UE 1  p. 65
9.2.1.6UE 2  p. 65
9.2.2Deployment scenarios  p. 66
9.2.2.1Administration of MC service, SIP core and EPS  p. 66
9.2.2.1.1General  p. 66
9.2.2.1.2Common administration of all planes  p. 66
9.2.2.1.3MC service provider separate from SIP core and EPS  p. 67
9.2.2.1.4MC service provider administers SIP core, separate from EPS  p. 67
9.2.2.1.5SIP core partially administered by both PLMN operator and MC service provider  p. 68
9.2.2.1.6PLMN operator administers SIP core with SIP identities administered by MC service provider  p. 69
9.2.2.2MC service user database, SIP database and HSS  p. 70
9.2.2.3Control of bearers by SIP core and MC service server  p. 73
9.2.2.3.1General  p. 73
9.2.2.3.2Control of bearers by SIP core  p. 73
9.2.2.3.3Control of bearers by MC service server  p. 73
9.3Architecture model for off-network operations  p. 74
9.3.1Off-network architectural model diagram  p. 74
9.3.2UE 3  p. 74
9.3.3UE 4  p. 75
9.3.4Offline common services server  p. 75
9.4Architecture model for roaming  p. 75
10Procedures and information flows  p. 75
10.1MC service configuration  p. 75
10.1.1General  p. 75
10.1.1.1MC service configuration on primary MC system |R15|  p. 75
10.1.1.2MC service configuration for migration to partner MC system |R15|  p. 77
10.1.2Information flows for MC service configuration  p. 79
10.1.2.1Store group configuration request  p. 79
10.1.2.1aStore target group configuration request |R19|  p. 79
10.1.2.2Store group configuration response  p. 80
10.1.2.3Get group configuration request  p. 80
10.1.2.4Get group configuration response  p. 80
10.1.2.5Subscribe group configuration request  p. 80
10.1.2.5aSubscribe group policy request |R17|  p. 81
10.1.2.6Subscribe group configuration response  p. 81
10.1.2.6aSubscribe group policy response |R17|  p. 81
10.1.2.7Notify group configuration request  p. 81
10.1.2.7aNotify group policy request |R17|  p. 82
10.1.2.8Notify group configuration response  p. 82
10.1.2.8aNotify group policy response |R17|  p. 82
10.1.2.9Get functional alias configuration request |R15|  p. 82
10.1.2.10Get functional alias configuration response |R15|  p. 83
10.1.2.11Subscribe functional alias configuration request |R15|  p. 83
10.1.2.12Subscribe functional alias configuration response |R15|  p. 83
10.1.2.13Notify functional alias configuration request |R15|  p. 83
10.1.2.14Notify functional alias configuration response |R15|  p. 84
10.1.2.15Void  p. …
10.1.2.16Void  p. …
10.1.2.17Void  p. …
10.1.2.18Void  p. …
10.1.2.19Void  p. …
10.1.2.20Void  p. …
10.1.2.21Void  p. …
10.1.2.22Void  p. …
10.1.2.23Void  p. …
10.1.2.24Void  p. …
10.1.2.25Void  p. …
10.1.3MC service UE configuration data  p. 84
10.1.3.1General  p. 84
10.1.3.2Procedures  p. 84
10.1.3.3Structure of UE configuration data  p. 85
10.1.4MC service user profile  p. 85
10.1.4.1General  p. 85
10.1.4.2Information flows for MC service user profile  p. 86
10.1.4.2.1Get MC service user profile request  p. 86
10.1.4.2.2Get MC service user profile response  p. 87
10.1.4.2.3Notification for MC service user profile data update  p. 87
10.1.4.2.4Get updated MC service user profile data request  p. 87
10.1.4.2.5Get updated MC service user profile data response  p. 87
10.1.4.2.6Update MC service user profile data request  p. 87
10.1.4.2.6aUpdate target MC service user profile data request |R19|  p. 88
10.1.4.2.7Update MC service user profile data response  p. 88
10.1.4.2.8Update pre-selected MC service user profile request  p. 88
10.1.4.2.9Update pre-selected MC service user profile response  p. 88
10.1.4.2.10Update selected MC service user profile request  p. 89
10.1.4.2.11Update selected MC service user profile response  p. 89
10.1.4.3MC service user obtains the MC service user profile(s) from the network  p. 89
10.1.4.3.1MC service user receiving MC service in primary MC system |R15|  p. 89
10.1.4.3.2MC service user receiving MC service from a partner MC system |R15|  p. 90
10.1.4.4MC service user receives updated MC service user profile data from the network  p. 92
10.1.4.5MC service user updates MC service user profile data to the network  p. 92
10.1.4.6Updating the pre-selected MC service user profile  p. 93
10.1.4.7Updating the selected MC service user profile for an MC service  p. 94
10.1.5MC service group configuration management  p. 96
10.1.5.1Store group configurations at the group management server  p. 96
10.1.5.2Retrieve group configurations at the group management client  p. 96
10.1.5.3Subscription and notification for group configuration data at group management client  p. 97
10.1.5.3aSubscription and notification for group policy at MC service server |R17|  p. 98
10.1.5.4Structure of group configuration data  p. 99
10.1.5.5Dynamic data associated with a group  p. 99
10.1.5.5.1Dynamic data associated with a group in MC service server |R16|  p. 99
10.1.5.5.2Dynamic data associated with a group in group management server |R16|  p. 99
10.1.5.6Subscription and notification for dynamic data associated with a group |R15|  p. 100
10.1.5.6.0General |R17|  p. 100
10.1.5.6.1Information flows for subscription, notification and cancellation for dynamic data associated with a group  p. 101
10.1.5.6.1.1Subscribe group dynamic data request  p. 101
10.1.5.6.1.2Subscribe group dynamic data response  p. 101
10.1.5.6.1.3Notify group dynamic data request  p. 101
10.1.5.6.1.4Notify group dynamic data response  p. 101
10.1.5.6.1.5Cancel group dynamic data subscription request   p. 102
10.1.5.6.1.6Cancel group dynamic data subscription response   p. 102
10.1.5.6.2Procedure for subscription, notification and cancellation for dynamic data associated with a group by the MC service client  p. 102
10.1.5.6.2.1Subscription   p. 102
10.1.5.6.2.2Notification   p. 102
10.1.5.6.2.3Cancellation   p. 103
10.1.5.6.3Procedure for subscription, notification and cancellation for dynamic data associated with a group by the group management server |R16|  p. 104
10.1.5.6.3.1Subscription   p. 104
10.1.5.6.3.2Notification   p. 104
10.1.5.6.3.3Cancellation   p. 105
10.1.5.6.4Procedures for subscription, notification and cancellation for dynamic data associated with a group by the location management server |R19|  p. 105
10.1.5.6.4.1Subscription  p. 105
10.1.5.6.4.2Notification  p. 105
10.1.5.6.4.3Cancellation  p. 106
10.1.6MC service UE migration |R15|  p. 106
10.1.6.1MC service UE obtains migration connectivity information of partner MC system  p. 106
10.1.6.2Void  p. …
10.1.7Functional alias configuration management |R15|  p. 107
10.1.7.1Retrieve functional alias configurations from the functional alias management server  p. 107
10.1.7.2Subscription and notification for functional alias configuration data  p. 107
10.1.7.3Dynamic data associated with a functional alias |R17|  p. 108
10.1.7.3.1Dynamic data associated with a functional alias in MC service server  p. 108
10.2Group management (on-network)  p. 109
10.2.1General  p. 109
10.2.2Information flows for group management  p. 109
10.2.2.1Group creation request  p. 109
10.2.2.2Group creation response  p. 110
10.2.2.3Group regroup request (group management client - group management server)  p. 110
10.2.2.4Group regroup response (group management server - group management client)  p. 110
10.2.2.5Group regroup teardown request  p. 110
10.2.2.6Group regroup teardown response  p. 111
10.2.2.7Group creation notify  p. 111
10.2.2.8Group regroup notify  p. 111
10.2.2.9Group regroup teardown notify  p. 111
10.2.2.10Group regroup teardown notification  p. 112
10.2.2.11Group regroup teardown notification response  p. 112
10.2.2.12Group regroup request (group management server - group management server)  p. 112
10.2.2.13Group regroup response (group management server - group management server)  p. 112
10.2.2.14Group regroup notification  p. 113
10.2.2.15Group regroup notification response  p. 113
10.2.2.16Group information query request  p. 113
10.2.2.17Group information query response  p. 113
10.2.2.18Group membership update request  p. 114
10.2.2.19Group membership update response  p. 114
10.2.2.20Group membership notification  p. 114
10.2.2.21Group deletion request  p. 115
10.2.2.22Group deletion response  p. 115
10.2.2.23Group deletion notification  p. 115
10.2.2.24Group information provision request |R15|  p. 115
10.2.2.25Group information provision response |R15|  p. 115
10.2.2.26Group information request |R15|  p. 116
10.2.2.27Group information response |R15|  p. 116
10.2.2.28Group information subscribe request |R15|  p. 116
10.2.2.29Group information subscribe response |R15|  p. 116
10.2.2.30Group information notify request |R15|  p. 117
10.2.2.31Group information notify response |R15|  p. 117
10.2.3Group creation  p. 117
10.2.4Group regrouping  p. 119
10.2.4.1Temporary group formation - group regrouping within an MC system  p. 119
10.2.4.2Temporary group formation involving multiple MC systems  p. 121
10.2.4.2aTemporary group tear down within an MC system |R17|  p. 123
10.2.4.3Temporary group tear down involving multiple group host servers  p. 124
10.2.4.4Group regroup rules |R15|  p. 125
10.2.5Membership and affiliation list query  p. 126
10.2.5.1General  p. 126
10.2.5.2Procedure  p. 126
10.2.6Group membership  p. 126
10.2.6.1Group membership notification  p. 126
10.2.6.2Group membership update by authorized user  p. 127
10.2.7Group configuration for interconnection  p. 128
10.2.7.1Overview |R15|  p. 128
10.2.7.2Primary MC system provides group configuration to the partner MC system |R15|  p. 129
10.2.7.3Partner MC system requests group configuration from the primary MC system |R15|  p. 130
10.2.7.4Partner MC system subscribes to group configuration |R15|  p. 131
10.2.7.5Primary MC system notifies group configuration |R15|  p. 132
10.2.8Group deletion |R15|  p. 133
10.3Pre-established session (on-network)  p. 134
10.3.1General  p. 134
10.3.2Procedures  p. 134
10.3.2.1General  p. 134
10.3.2.2Pre-established session establishment  p. 134
10.3.2.3Pre-established session modification  p. 135
10.3.2.4Pre-established session release  p. 137
10.4Simultaneous session (on-network)  p. 138
10.4.1General  p. 138
10.5Use of UE-to-network relay  p. 138
10.5.1UE-to-network relay service authorization  p. 138
10.5.2UE-to-network relay MC service  p. 138
10.6General user authentication and authorization for MC services  p. 138
10.6.1Primary MC system |R15|  p. 138
10.6.2Interconnection partner MC system |R15|  p. 139
10.6.3Migration to partner MC system |R15|  p. 139
10.6.3.1General  p. 139
10.6.3.2Information flows  p. 140
10.6.3.2.1Migration service authorization request  p. 140
10.6.3.2.2Migration service authorization response  p. 140
10.6.3.2.3Migration service de-authorization notification |R18|  p. 140
10.6.3.2.4MC service authorization notification |R18|  p. 141
10.6.3.3Procedures  p. 141
10.6.3.3.1Migration service authorization procedure |R18|  p. 141
10.6.3.3.2Migration service de-authorization procedure initiated by MC service server |R18|  p. 143
10.6.3.3.2.1Migrated MC service user returns back to its primary MC system  p. 143
10.6.3.3.2.2Migrated MC service user migrate to another partner MC system  p. 144
10.7Use of MBMS transmission  p. 145
10.7.1General  p. 145
10.7.2Information flows for MBMS transmission  p. 145
10.7.2.1MBMS bearer announcement  p. 145
10.7.2.2MBMS listening status report  p. 146
10.7.2.3MBMS suspension reporting instruction  p. 146
10.7.2.4Discover bearer request  p. 147
10.7.2.5Discover bearer response  p. 147
10.7.2.6Media distribution request  p. 147
10.7.2.7Media distribution response  p. 148
10.7.2.8Identify multicast participants request  p. 148
10.7.2.9Remove call from bearer request  p. 148
10.7.2.10Media distribution release |R15|  p. 148
10.7.2.11Media broadcasting notification |R15|  p. 148
10.7.2.12Group status notification |R16|  p. 148
10.7.2.13MBMS suspension report |R17|  p. 149
10.7.3Procedures for MBMS usage  p. 149
10.7.3.1Use of pre-established MBMS bearers  p. 149
10.7.3.1.1General  p. 149
10.7.3.1.2Procedure  p. 149
10.7.3.2Use of dynamic MBMS bearer establishment  p. 151
10.7.3.3Switching from MBMS bearer to unicast bearer  p. 152
10.7.3.4Use of MBMS bearer for application level control signalling  p. 153
10.7.3.4.1Description  p. 153
10.7.3.4.2Procedure  p. 153
10.7.3.5MBMS bearer announcement over MBMS bearer  p. 154
10.7.3.5.1Description  p. 154
10.7.3.5.2Procedure  p. 154
10.7.3.6MBMS bearer quality detection  p. 156
10.7.3.6.1Description  p. 156
10.7.3.6.2Procedure  p. 156
10.7.3.7Service continuity in MBMS scenarios  p. 157
10.7.3.7.1General  p. 157
10.7.3.7.2Service continuity when moving from one MBSFN to another  p. 157
10.7.3.7.3Service continuity with a UE-to-Network relay  p. 160
10.7.3.8MBMS suspension notification  p. 162
10.7.3.8.1Description  p. 162
10.7.3.8.2Procedure  p. 162
10.7.3.9Multi-server bearer coordination  p. 163
10.7.3.9.1General  p. 163
10.7.3.9.2Procedures  p. 163
10.7.3.9.2.1MBMS bearer coordination independent on broadcasted media   p. 163
10.7.3.9.2.2MBMS bearer coordination within one group call   p. 165
10.7.3.10MBMS bearer event notification |R15|  p. 167
10.7.3.10.1General  p. 167
10.7.3.10.2Procedure  p. 168
10.7.3.11Use of FEC to protect MBMS transmissions |R15|  p. 168
10.7.3.11.1General  p. 168
10.7.3.11.2FEC encoding by the BM-SC  p. 169
10.7.3.11.3FEC encoding by the MC service server  p. 170
10.7.3.12Header compression over MBMS with ROHC |R15|  p. 171
10.7.3.12.1General  p. 171
10.7.3.12.2Header compression by the MC service server  p. 171
10.7.3.12.3Header compression by the BM-SC  p. 172
10.7.3.13Use of MBMS bearer for group status |R16|  p. 173
10.8Affiliation and de-affiliation to/from MC service group(s)  p. 174
10.8.1General  p. 174
10.8.2Information flows  p. 174
10.8.2.1MC service group affiliation request  p. 174
10.8.2.2MC service group affiliation request (MC service server - MC service server)  p. 174
10.8.2.3MC service group affiliation response  p. 174
10.8.2.4MC service group affiliation response (MC service server - MC service server)  p. 175
10.8.2.5Void  p. …
10.8.2.6MC service group de-affiliation request  p. 175
10.8.2.7MC service group de-affiliation request (MC service server - MC service server)  p. 175
10.8.2.8MC service group de-affiliation response  p. 175
10.8.2.9MC service group de-affiliation response (MC service server - MC service server)  p. 176
10.8.2.10Void  p. …
10.8.2.11MC service group affiliation change request  p. 176
10.8.2.12MC service group affiliation change response  p. 176
10.8.2.13MC service group de-affiliation notification |R15|  p. 177
10.8.2.14Notify group dynamic data request |R16|  p. 177
10.8.3Affiliation  p. 177
10.8.3.1MC service group affiliation procedure  p. 177
10.8.3.2Affiliation to MC service group(s) defined in partner MC system without topology hiding  p. 178
10.8.3.2.1Functional description  p. 178
10.8.3.2.2Procedure  p. 179
10.8.3.2aAffiliation to MC service group(s) defined in partner MC system using topology hiding |R15|  p. 180
10.8.3.2a.1Functional description  p. 180
10.8.3.2a.2Procedure  p. 180
10.8.4De-affiliation from MC service group(s)  p. 182
10.8.4.1General  p. 182
10.8.4.2MC service group de-affiliation procedure  p. 182
10.8.4.3De-affiliation from MC service group(s) defined in partner MC system  p. 183
10.8.4.4MC server initiated group de-affiliation procedure |R15|  p. 185
10.8.4.5MC server initiated group de-affiliation from group defined in partner MC system |R15|  p. 185
10.8.5Remote change of affiliation  p. 187
10.8.5.1Remote change of affiliation for groups defined in primary MC system  p. 187
10.8.5.1.1Authorized user remotely changes another MC service user's affiliated MC service group(s) - mandatory mode  p. 187
10.8.5.1.2Authorized user remotely changes another MC service user's affiliated MC service group(s) - negotiated mode  p. 188
10.8.5.2Remote change of affiliation for groups defined in partner MC system  p. 190
10.8.5.2.1Authorized user remotely changes another MC service user's affiliated MC service group(s) defined in partner MC system - mandatory mode  p. 190
10.9Location management (on-network)  p. 191
10.9.1General  p. 191
10.9.2Information flows for location information  p. 192
10.9.2.1Location reporting configuration  p. 192
10.9.2.2Location information report  p. 193
10.9.2.3Location information request  p. 195
10.9.2.4Location reporting trigger  p. 197
10.9.2.4aLocation reporting trigger cancel |R19|  p. 199
10.9.2.5Location information subscription request  p. 199
10.9.2.6Location information subscription response  p. 201
10.9.2.7Location information notification  p. 201
10.9.2.8Location information cancel subscription request |R16|  p. 202
10.9.2.9Location information cancel subscription response |R16|  p. 203
10.9.2.10Void  p. …
10.9.2.11Location information history status request |R17|  p. 204
10.9.2.12Location information history status report |R17|  p. 205
10.9.2.13Location information history request |R17|  p. 206
10.9.2.14Location information history report |R17|  p. 207
10.9.2.15Location information history cancel request |R17|  p. 209
10.9.2.16Location information history cancel response |R17|  p. 209
10.9.2.17Location reporting temporary configuration request |R18|  p. 210
10.9.2.18Location reporting temporary configuration response |R18|  p. 210
10.9.2.19Restrict location information dissemination request |R18|  p. 211
10.9.2.20Restrict location information dissemination response |R18|  p. 211
10.9.2.21Restrict location information dissemination notification |R18|  p. 212
10.9.2.22Location reporting trigger override indication |R19|  p. 212
10.9.2.23Location reporting cancel trigger override indication |R19|  p. 213
10.9.3Procedure  p. 213
10.9.3.1Event-triggered location reporting procedure  p. 213
10.9.3.2On-demand location reporting procedure  p. 214
10.9.3.3Client-triggered location reporting procedure  p. 215
10.9.3.4Event-triggered location reporting cancel procedure  p. 216
10.9.3.4aClient-triggered location reporting cancel procedure targeting MC service user(s) |R19|  p. 217
10.9.3.4bClient-triggered location reporting cancel procedure targeting MC service group(s) |R19|  p. 218
10.9.3.5Location information subscription procedure  p. 218
10.9.3.6Usage of location information procedure  p. 220
10.9.3.6.1Event-trigger location information notification procedure  p. 220
10.9.3.6.2On-demand usage of location information procedure  p. 220
10.9.3.7Location information cancel subscription procedure |R16|  p. 221
10.9.3.8Location management using functional alias |R16|  p. 222
10.9.3.8.1Client-triggered one-time location information report  p. 222
10.9.3.8.2Client-triggered periodic location information report  p. 223
10.9.3.8.3Client-triggered location reporting cancel procedure targeting functional alias(es) |R19|  p. 225
10.9.3.9Usage of location history reporting procedure |R17|  p. 226
10.9.3.9.1General  p. 226
10.9.3.9.2Report location history procedure  p. 226
10.9.3.9.2.1On-demand report location history procedure (LMC - LMS)  p. 226
10.9.3.9.2.2On-demand report location history procedure  p. 227
10.9.3.9.3Usage of status location history reporting procedure  p. 228
10.9.3.9.3.1Status location history reporting procedure (LMC - LMS)  p. 228
10.9.3.9.3.2On-demand status location history reporting procedure (LMS - LMC)  p. 229
10.9.3.9.3.3On-demand status location history reporting procedure  p. 229
10.9.3.9.4Usage of cancel location history reporting procedure  p. 230
10.9.3.9.4.1General  p. 230
10.9.3.9.4.2Cancel location history reporting procedure (LMS - LMC)  p. 230
10.9.3.9.4.3Cancel location history reporting procedure  p. 231
10.9.3.10Usage of location information across MC systems procedure |R18|  p. 232
10.9.3.10.1General  p. 232
10.9.3.10.2On-demand request of location information procedure  p. 232
10.9.3.10.3Event-triggered location information notification procedure  p. 233
10.9.3.10.4Location information subscription procedure  p. 234
10.9.3.10.5Location information cancel subscription procedure  p. 236
10.9.3.10.6Location reporting temporary configuration procedure  p. 237
10.9.3.11Restrict location information dissemination procedure |R18|  p. 239
10.9.3.12Location reporting trigger override |R19|  p. 240
10.9.3.12.1General  p. 240
10.9.3.12.2Location reporting trigger override procedure  p. 240
10.9.3.12.3Cancel location reporting trigger override procedure  p. 241
10.10Emergency Alert  p. 242
10.10.1On-network emergency alert  p. 242
10.10.1.1General  p. 242
10.10.1.1AInformation flows |R18|  p. 243
10.10.1.1A.1MC service emergency alert request  p. 243
10.10.1.1A.2MC service emergency alert response  p. 243
10.10.1.1A.3MC service emergency alert cancel request  p. 243
10.10.1.1A.4MC service emergency alert cancel response  p. 244
10.10.1.1A.5MC service emergency alert area notification  p. 244
10.10.1.2MC service emergency alert  p. 245
10.10.1.2.1MC service emergency alert initiation  p. 245
10.10.1.2.1.1General   p. 245
10.10.1.2.1.2MC service group emergency alert initiation   p. 246
10.10.1.2.1.3MC service individual emergency alert initiation   p. 247
10.10.1.2.2MC service emergency alert cancel  p. 248
10.10.1.2.2.1General   p. 248
10.10.1.2.2.2MC service group emergency alert cancel   p. 248
10.10.1.2.2.3MC service individual emergency alert cancel   p. 250
10.10.1.2.3Entering MC service emergency alert area |R16|  p. 250
10.10.1.2.4Leaving MC service emergency alert area |R16|  p. 251
10.10.2Off-network emergency alert  p. 253
10.10.2.1General  p. 253
10.10.2.1AInformation flows |R18|  p. 253
10.10.2.1A.1MC service emergency alert announcement  p. 253
10.10.2.1A.2MC service emergency alert cancel announcement  p. 253
10.10.2.2MC service emergency alert  p. 253
10.10.2.2.1Emergency alert initiation  p. 253
10.10.2.2.2Emergency alert cancel  p. 255
10.10.3Ad hoc group emergency alert |R18|  p. 256
10.10.3.1General  p. 256
10.10.3.2Information flows  p. 256
10.10.3.2.1Ad hoc group emergency alert request (MC service client - MC service server)  p. 256
10.10.3.2.2Ad hoc group emergency alert request (MC service server - MC service client)  p. 256
10.10.3.2.2aAd hoc group emergency alert request return  p. 257
10.10.3.2.3Ad hoc group emergency alert response  p. 257
10.10.3.2.4Ad hoc group emergency alert cancel request  p. 258
10.10.3.2.4aAd hoc group emergency alert cancel request return  p. 258
10.10.3.2.5Ad hoc group emergency alert cancel response  p. 259
10.10.3.2.6Ad hoc group emergency alert participants list notification  p. 259
10.10.3.2.7Ad hoc group emergency alert get userlist request  p. 259
10.10.3.2.8Ad hoc group emergency alert get userlist response  p. 260
10.10.3.2.9Ad hoc group emergency alert user add notification  p. 260
10.10.3.2.10Ad hoc group emergency alert user remove notification  p. 260
10.10.3.2.11Ad hoc group emergency alert notify  p. 261
10.10.3.2.12Ad hoc group emergency alert modify request |R19|  p. 261
10.10.3.2.12aAd hoc group emergency alert modify request return |R19|  p. 262
10.10.3.2.13Ad hoc group emergency alert modify response |R19|  p. 262
10.10.3.3Procedures within single MC system  p. 263
10.10.3.3.1Ad hoc group emergency alert initiation  p. 263
10.10.3.3.2Ad hoc group emergency alert cancel  p. 265
10.10.3.3.3Entering an ongoing ad hoc group emergency alert  p. 267
10.10.3.3.4Leaving an ad hoc group emergency alert  p. 268
10.10.3.3.5Modifying the criteria for determining the participants during an ongoing ad hoc group emergency alert |R19|  p. 269
10.10.3.4Procedures within multiple MC systems  p. 270
10.10.3.4.1Ad hoc group emergency alert initiation  p. 270
10.10.3.4.2Updating the participant list of an ongoing ad hoc group emergency alert  p. 272
10.10.3.4.3Ad hoc group emergency alert cancel  p. 274
10.10.3.4.4Modifying the criteria for determining the participants during an ongoing ad hoc group emergency alert |R19|  p. 275
10.11MC service resource management (on-network) |R15|  p. 276
10.11.1General  p. 276
10.11.2Request for unicast resources at session establishment - SIP core based  p. 277
10.11.2aRequest for unicast resources at session establishment - MC service server based |R17|  p. 278
10.11.2a.1General  p. 278
10.11.2a.2Procedure  p. 278
10.11.3Request for modification of unicast resources  p. 279
10.11.4Management of multicast media bearers  p. 280
10.11.5Request for resources with shared priority  p. 281
10.11.5.1General  p. 281
10.11.5.2Procedure  p. 281
10.11.6Request for media resources from MC service server  p. 282
10.11.6.1General  p. 282
10.11.6.2Procedure  p. 282
10.12Priority Management |R15|  p. 283
10.12.1General  p. 283
10.12.2Information flows  p. 283
10.12.2.1MC priority request  p. 283
10.12.3Procedure for priority coordination between multiple MC service servers  p. 284
10.13Functional alias management (on-network) |R15|  p. 285
10.13.1General  p. 285
10.13.2Information flows for functional alias management  p. 285
10.13.2.1Active functional alias information user query request  p. 285
10.13.2.1aActive functional alias information usage query request |R16|  p. 286
10.13.2.2Active functional alias information user query response  p. 286
10.13.2.2aActive functional alias information usage query response |R16|  p. 286
10.13.2.3Functional alias activation request  p. 286
10.13.2.4Functional alias activation response  p. 287
10.13.2.5Functional alias de-activation request  p. 287
10.13.2.6Functional alias de-activation response  p. 287
10.13.2.7Functional alias status notification  p. 287
10.13.2.8Functional alias take over request  p. 288
10.13.2.9Functional alias take over response  p. 288
10.13.2.10Functional alias revoke notification  p. 288
10.13.2.11Subscribe functional alias request |R16|  p. 288
10.13.2.12Subscribe functional alias response |R16|  p. 288
10.13.2.13Notify functional alias request |R16|  p. 289
10.13.2.14Notify functional alias response |R16|  p. 289
10.13.2.15Unsubscribe functional alias request |R16|  p. 289
10.13.2.16Unsubscribe functional alias response |R16|  p. 289
10.13.2.17Functional alias to group binding request |R17|  p. 290
10.13.2.18Functional alias to group binding response |R17|  p. 290
10.13.2.19Functional alias to group unbinding request |R17|  p. 290
10.13.2.20Functional alias to group unbinding response |R17|  p. 290
10.13.3Authorised MC service user retrieves active functional alias(es) for certain MC service user(s)  p. 291
10.13.4MC service user activates functional alias(es) within an MC system  p. 291
10.13.5MC service user de-activates functional alias(es) within an MC system  p. 292
10.13.6Authorised MC service user takes over functional alias(es) within an MC system  p. 293
10.13.7Authorised MC service user retrieves MC service user(s) for certain active functional alias(es) |R16|  p. 294
10.13.8Automatic activation of functional alias(es) within an MC system |R16|  p. 295
10.13.9Automatic deactivation of functional alias(es) within an MC system |R16|  p. 296
10.13.10Subscription and notification for functional alias |R16|  p. 297
10.13.10.1General  p. 297
10.13.10.2Subscription for functional alias procedure  p. 297
10.13.10.3Notification for functional alias procedure  p. 299
10.13.10.4Unsubscription for functional alias procedure  p. 299
10.13.11Functional alias to group binding |R17|  p. 299
10.13.11.1General  p. 299
10.13.11.2Functional alias to group binding  p. 299
10.13.11.3Functional alias to group unbinding  p. 299
10.14Generic procedures for interconnection |R15|  p. 300
10.14.1General  p. 300
10.14.2Generic call procedure with topology hiding  p. 300
10.14.2.1General  p. 300
10.14.2.2Procedure for calls with topology hiding  p. 300
10.14.3Generic call procedure for enforcement of local MC service group configuration  p. 302
10.14.3.1General  p. 302
10.14.3.2MC service group call initiated in the partner MC system of the MC service group  p. 302
10.14.3.3MC service group call request received from the primary MC system of the MC service group  p. 303
10.14.4Generic call procedure for media replication in participating MC system in MC service group calls  p. 304
10.14.4.1General  p. 304
10.14.4.2Media replication in the partner MC system of the MC service group  p. 304
10.15Preconfigured regrouping |R17|  p. 305
10.15.1General  p. 305
10.15.2Information flows for preconfigured regrouping  p. 306
10.15.2.1Preconfigured regroup request (MC service client - MC service server)  p. 306
10.15.2.2Preconfigured regroup request (MC service server - MC service client)  p. 306
10.15.2.3Preconfigured regroup request (MC service server - MC service server)  p. 307
10.15.2.4Preconfigured regroup response (MC service client - MC service server)  p. 307
10.15.2.5Preconfigured regroup response (MC service server - MC service client)  p. 307
10.15.2.6Preconfigured regroup response (MC service server - MC service server)  p. 307
10.15.2.7Preconfigured regroup cancel request (MC service client - MC service server)  p. 308
10.15.2.8Preconfigured regroup cancel request (MC service server - MC service client)  p. 308
10.15.2.9Preconfigured regroup cancel request (MC service server - MC service server)  p. 308
10.15.2.10Preconfigured regroup cancel response (MC service client - MC service server)  p. 308
10.15.2.11Preconfigured regroup cancel response (MC service server - MC service client)  p. 309
10.15.2.12Preconfigured regroup cancel response (MC service server - MC service server)  p. 309
10.15.2.13Preconfigured regroup reject (MC service server - MC service client)  p. 309
10.15.2.14Preconfigured regroup reject (MC service server - MC service server)  p. 310
10.15.2.15Preconfigured user regroup remove request (MC service server - MC service client) |R18|  p. 310
10.15.2.16Preconfigured user regroup remove response (MC service client - MC service server) |R18|  p. 310
10.15.2.17Preconfigured regroup request return (MC service server - MC service client) |R19|  p. 310
10.15.3Regroup with preconfigured group  p. 311
10.15.3.1General  p. 311
10.15.3.2Preconfigured regroup procedures in a single MC system  p. 311
10.15.3.2.1Preconfigured Group Regroup formation in a single MC system  p. 312
10.15.3.2.2Preconfigured User Regroup formation in a single MC system  p. 314
10.15.3.2.3Preconfigured regroup cancellation in a single MC system  p. 315
10.15.3.3Preconfigured regroup procedures in multiple MC systems  p. 316
10.15.3.3.1Preconfigured Group Regroup formation in multiple MC systems  p. 317
10.15.3.3.2Preconfigured User Regroup formation in multiple MC systems  p. 319
10.15.3.3.3Preconfigured regroup cancellation in multiple MC systems  p. 321
10.15.3.3.4Preconfigured group regroup rejection in multiple MC systems  p. 322
10.15.3.4Other preconfigured regroup procedures  p. 324
10.15.3.4.1Adding newly affiliated user to preconfigured group regroup  p. 324
10.15.3.4.2Updating the MC service ID list in a preconfigured regroup group based on user regroup |R18|  p. 325
10.15.3.4.3Adding a user to regroup group due to communication request to the group being regrouped |R19|  p. 326
10.15.3.4.4Regroup group cancel notification due to communication request to the cancelled regroup group |R19|  p. 327
10.16Generic procedures for migration |R18|  p. 328
10.16.1General  p. 328
10.16.2Migration during an ongoing group communication  p. 328
10.16.2.1General  p. 328
10.16.2.2Procedure  p. 328
10.16.2.3Void  p. …
10.16.2.3.1Void  p. …
10.16.3Private call using functional alias towards a partner MC system  p. 329
10.16.3.1General  p. 329
10.16.3.2Information flows  p. 329
10.16.3.2.1MC service functional alias resolution request  p. 329
10.16.3.2.2MC service functional alias resolution response  p. 330
10.16.3.3Procedure  p. 330
10.16.4Migration during an onging private communication  p. 332
10.16.4.1General  p. 332
10.16.4.2Procedure  p. 332
10.16.5Generic private call procedure towards a migrated MC service user  p. 334
10.16.5.1General  p. 334
10.16.5.2Private call redirection  p. 334
10.16.5.3Procedure  p. 334
10.16.6Ad hoc group call procedure towards a migrated MC service user |R19|  p. 336
10.16.6.1General  p. 336
10.16.6.2Information flows  p. 336
10.16.6.2.1Ad hoc group call redirection notify  p. 336
10.16.6.3Procedure  p. 337
10.16.7Migration during Ad hoc group call procedure |R19|  p. 339
10.16.7.1General  p. 339
10.16.7.2Information flows  p. 339
10.16.7.2.1Ad hoc group call redirection notify  p. 339
10.16.7.3Procedure for participants list provided by the Initiator  p. 340
10.16.7.4Procedure for criteria provided by the Initiator  p. 342
10.17Sharing administrative configuration between interconnected MC systems |R19|  p. 344
10.17.1General  p. 344
10.17.2Information flows  p. 345
10.17.2.1ACM data notification  p. 345
10.17.2.2Get ACM data request  p. 345
10.17.2.3Get ACM data response  p. 345
10.17.2.4Group membership update request  p. 345
10.17.2.5Group membership update response  p. 346
10.17.2.6Process indication  p. 346
10.17.2.7Interconnection group identity provision request  p. 346
10.17.2.8Interconnection group identity provision response  p. 347
10.17.2.9Add user configuration request  p. 347
10.17.2.10Add user configuration response  p. 348
10.17.2.11Remove user configuration request  p. 349
10.17.2.12Remove user configuration response  p. 349
10.17.2.13Update MC service UE initial configuration request  p. 350
10.17.2.14Update MC service UE initial configuration response  p. 350
10.17.2.15MC service user profile update request  p. 351
10.17.2.16MC service user profile update response  p. 351
10.17.3Common ACM procedures  p. 352
10.17.3.0Introduction  p. 352
10.17.3.1Pending requests  p. 352
10.17.3.1.1General  p. 352
10.17.3.1.2Procedure  p. 352
10.17.3.2Processing incoming requests automatically  p. 353
10.17.3.2.1General  p. 353
10.17.3.2.2Automation performed by ACM server  p. 353
10.17.3.2.3Automation performed by automated ACM client  p. 354
10.17.4ACM Group configuration management  p. 355
10.17.4.1ACM Group membership configuration  p. 355
10.17.4.1.1General  p. 355
10.17.4.1.2Procedure  p. 355
10.17.4.1.2.1Group membership update by authorized user from a partner MC system  p. 355
10.17.4.2Providing interconnection MC service group ID  p. 357
10.17.4.2.1General  p. 357
10.17.4.2.2Providing identity of interconnection MC service group  p. 357
10.17.5ACM user migration management  p. 359
10.17.5.1General  p. 359
10.17.5.2Adding users for migration to a partner MC system  p. 359
10.17.5.3Removing users for migration from a partner MC system  p. 361
10.17.6ACM updating MC service UE initial configuration for migration  p. 363
10.17.6.1General  p. 363
10.17.6.2Procedure  p. 363
10.17.7ACM updating MC service user profiles assigned from partner MC system  p. 365
10.17.7.1General  p. 365
10.17.7.2Procedure  p. 365
10.18Recording and replay |R19|  p. 367
10.18.1Service configuration  p. 367
10.18.1.1Service ID and user profile  p. 367
10.18.1.2Recording admin service configuration  p. 368
10.18.1.3Replay service configuration  p. 370
10.18.1.4Information flows for recording admin and replay service user profiles  p. 372
10.18.1.4.1Get recording admin and replay service user profile request  p. 372
10.18.1.4.2Get recording admin and replay service user profile response  p. 372
10.18.1.4.3Notification for recording admin and replay service user profile data update  p. 372
10.18.1.4.4Get updated recording admin and replay service user profile data request  p. 372
10.18.1.4.5Get updated recording admin and replay service user profile data response  p. 373
10.18.1.5Procedures for recording admin and replay service user profiles  p. 373
10.18.1.5.1Get recording admin and replay service user profile  p. 373
10.18.1.5.2Get updated recording admin and replay service user profile data  p. 373
10.18.2Target group and target user configuration  p. 374
10.18.2.1Store target group configuration at the GMS  p. 374
10.18.2.2Update target MC service user profile data to the CMS  p. 375
10.18.3Recording procedures  p. 376
10.18.3.1General  p. 376
10.18.3.2Procedure for recording communication sessions of an MC service user  p. 376
10.18.3.3Procedure for recording communication sessions of an MC service group  p. 377
10.18.4Replay procedure  p. 378
10.18.4.1General  p. 378
10.18.4.2Procedure for fetching a recording from a recording server  p. 378
11MC gateway UE |R18|  p. 379
11.1General  p. 379
11.2Functional Model  p. 380
11.2.0General  p. 380
11.2.1Functional model  p. 381
11.2.2.1General  p. 383
11.2.2.2Void  p. …
11.2.2.3Void  p. …
11.2.2.4Reference points MCX-n, CSC-n, SIP-1 and HTTP-1  p. 383
11.2.2.5Reference points GW-local (between the GW client and the GW server) |R19|  p. 383
11.2.3Void  p. …
11.3Using identities behind the MC gateway UE  p. 384
11.3.1General  p. 384
11.3.2When using separate IMS subscriptions  p. 384
11.3.3When sharing MC gateway UE's IMS subscription  p. 384
11.4Void  p. …
11.5Procedures and information flows  p. 385
11.5.0General |R19|  p. 385
11.5.1Void  p. …
11.5.23GPP access network related location information management |R19|  p. 385
11.5.2.1General  p. 385
11.5.2.2Information flows  p. 385
11.5.2.2.1MC GW location reporting configuration  p. 385
11.5.2.2.2MC GW location information report  p. 386
11.5.2.2.3MC GW location information request  p. 386
11.5.2.3Procedures  p. 386
11.5.2.3.1Event triggered location reporting procedure  p. 386
11.5.2.3.2On-demand location reporting procedure  p. 387
11.5.2.3.3Location reporting cancel procedure  p. 388
11.5.3MBMS support for MC clients residing on non-3GPP devices |R19|  p. 389
11.5.3.1General  p. 389
11.5.3.2Information flows  p. 389
11.5.3.2.1MC GW MBMS bearer announcement  p. 389
11.5.3.2.2MC GW MBMS listening status report  p. 390
11.5.3.2.3MC GW MapGroupToBearer request  p. 390
11.5.3.2.4MC GW MapGroupToBearer response  p. 390
11.5.3.2.5MC GW MBMS listening status report  p. 390
11.5.3.2.6MC GW MBMS bearer suspension indication  p. 391
11.5.3.2.7MC GW UnMapGroupToBearer request  p. 391
11.5.3.2.8MC GW UnMapGroupToBearer response  p. 391
11.5.3.3Procedures  p. 391
11.5.3.3.1Procedure for handling MBMS bearer announcement  p. 391
11.5.3.3.2Procedure for handling MapGroupToBearer message  p. 393
11.5.3.3.2AProcedure for handling UnmapGroupFromBearer message  p. 394
11.5.3.3.3Procedure for MBMS bearer suspension notification  p. 395
11.5.3.3.4Procedure for reporting MBMS listening status  p. 396
11.5.4Void  p. …
A(Normative)  Configuration data for MC services  p. 398
A.1General  p. 398
A.2MC service UE configuration data  p. 399
A.3MC service user profile configuration data  p. 399
A.4Group configuration data  p. 399
A.5MC service configuration data  p. 407
A.6Initial MC service UE configuration data  p. 407
A.7Void  p. …
A.8Location user profile configuration data |R18|  p. 409
A.9ACM client user profile configuration data |R19|  p. 413
A.10Initial recording admin UE and/or replay UE configuration data |R19|  p. 414
A.11Recording admin and/or replay service user profile configuration data |R19|  p. 415
BService continuity for MC service  p. 418
B.1Service continuity between on-network MC service and UE-to-network relay MC service  p. 418
CApplication Priority |R17|  p. 422
C.1Use of application priorities  p. 422
DConsiderations for MC gateway UE selection |R18|  p. 424
D.1General  p. 424
D.2Potential operating Conditions  p. 424
EMC gateway UE routing capabilities |R18|  p. 424
E.1General  p. 424
E.2MC client IP address association  p. 425
E.3IP address association using the MC gateway UE  p. 425
$Change history  p. 427