| |
Figure 5.2.6-1 | MC service on-network architecture showing MBMS |
Figure 6-1 | Business relationships for MC services |
Figure 6-2 | Additional business relationships for mutual aid |
Figure 7.3.1.2-1 | Functional model for application plane for an MC system |
Figure 7.3.1.2-2 | Functional model for signalling control plane |
Figure 7.3.1.2-3 | Relationships between reference points of MC service application plane and signalling control planes |
Figure 7.3.1.3-1 | Functional model for application plane of a Recording admin UE |
Figure 7.3.1.3-2 | Functional model for application plane of a Replay UE |
Figure 7.3.2-1 | Functional model for MC service off-network operation |
Figure 8.1.3.2-1 | MC service group ID management in off-network operation |
Figure 8.3.2-1 | The relationship of MC service group IDs, PSIs and MC service servers |
Figure 9.2.1.1-1 | On-network architectural model |
Figure 9.2.2.1.2-1 | Common administration of all services by one operator |
Figure 9.2.2.1.3-1 | MC service provider administers MC service separately from SIP core and EPS |
Figure 9.2.2.1.4-1 | MC service provider provision of SIP core, separate domain from EPS |
Figure 9.2.2.1.5-1 | MC service provider partial provision of SIP core, separate domain from EPS |
Figure 9.2.2.1.6-1 | MC service provider provides identities to PLMN operator SIP core |
Figure 9.2.2.2-1 | Collocation of MC service user database and SIP database with HSS |
Figure 9.2.2.2-2 | Shared PLMN operator and MC service provider based deployment of MC service - SIP database collocated with HSS with separate MC service user database |
Figure 9.2.2.2-3 | Shared PLMN operator and MC service provider based deployment of MC service - MC service user database and SIP database deployed together, with separate HSS |
Figure 9.2.2.2-4 | Shared PLMN operator and MC service provider based deployment of MC service - separate HSS, MC service user database and SIP database |
Figure 9.2.2.3.2-1 | Bearer control by SIP core |
Figure 9.2.2.3.3-1 | Bearer control by MC service server |
Figure 9.3.1-1 | Off-network architectural model for inter-UE communication where no relay function is used |
Figure 9.3.1-2 | Off-network architectural model for configuration management and group management |
Figure 10.1.1.1-1 | MC service UE configuration time sequence and associated configuration data |
Figure 10.1.1.2-1 | MC service UE configuration sequence for migration |
Table 10.1.2.1-1 | Store group configuration request |
Table 10.1.2.1a-1 | Store target group configuration request |
Table 10.1.2.2-1 | Store group configuration response |
Table 10.1.2.3-1 | Get group configuration request |
Table 10.1.2.4-1 | Get group configuration response |
Table 10.1.2.5-1 | Subscribe group configuration request |
Table 10.1.2.5a-1 | Subscribe group policy request |
Table 10.1.2.6-1 | Subscribe group configuration response |
Table 10.1.2.6a-1 | Subscribe group policy response |
Table 10.1.2.7-1 | Notify group configuration request |
Table 10.1.2.7a-1 | Notify group policy request |
Table 10.1.2.8-1 | Notify group configuration response |
Table 10.1.2.8a-1 | Notify group policy response |
Table 10.1.2.9-1 | Get functional alias configuration request |
Table 10.1.2.10-1 | Get functional alias configuration response |
Table 10.1.2.11-1 | Subscribe functional alias configuration request |
Table 10.1.2.12-1 | Subscribe functional alias configuration response |
Table 10.1.2.13-1 | Notify functional alias configuration request |
Table 10.1.2.14-1 | Notify functional alias configuration response |
Figure 10.1.3.2-1 | MC service UE obtains the configuration data |
Figure 10.1.4.1-1 | The relationship of MC service user, MC service IDs, MC service user profile and MC services |
Table 10.1.4.2.1-1 | Get MC service user profile request |
Table 10.1.4.2.2-1 | Get MC service user profile response |
Table 10.1.4.2.3-1 | Notification for MC service user profile data update |
Table 10.1.4.2.4-1 | Get updated MC service user profile data request |
Table 10.1.4.2.5-1 | Get updated MC service user profile data response |
Table 10.1.4.2.6-1 | Update MC service user profile data request |
Table 10.1.4.2.6a-1 | Update target MC service user profile data request |
Table 10.1.4.2.7-1 | Update MC service user profile data response |
Table 10.1.4.2.8-1 | Update pre-selected MC service user profile request |
Table 10.1.4.2.9-1 | Update pre-selected MC service user profile response |
Table 10.1.4.2.10-1 | Update selected MC service user profile request |
Table 10.1.4.2.11-1 | Update selected MC service user profile response |
Figure 10.1.4.3.1-1 | MC service user obtains the MC service user profile(s) from the network |
Figure 10.1.4.3.2-1 | Retrieval of user profile in partner MC system |
Figure 10.1.4.4-1 | MC service user receives updated MC service user profile data from the network |
Figure 10.1.4.5-1 | MC service user updates MC service user profile data to the network |
Figure 10.1.4.6-1 | MC service user updates the pre-selected MC service user profile |
Figure 10.1.4.7-1 | MC service user updates the selected MC service user profile |
Figure 10.1.5.1-1 | Store group configurations at group management server |
Figure 10.1.5.2-1 | Retrieve group configurations at group management client |
Figure 10.1.5.3-1 | Subscription for group configurations at group management client |
Figure 10.1.5.3-2 | Notification of group configurations to group management client |
Figure 10.1.5.3a-1 | Subscription for group policy at MC service server |
Figure 10.1.5.3a-2 | Notification of group policy to MC service server |
Table 10.1.5.5.1-1 | Dynamic data associated with a group |
Table 10.1.5.5.2-1 | Affiliation status in group management server |
Table 10.1.5.5.2-2 | Regroup status in group management server |
Table 10.1.5.5.2-3 | Emergency status in group management server |
Table 10.1.5.6.1.1-1 | Subscribe group dynamic data request |
Table 10.1.5.6.1.2-1 | Subscribe group dynamic data response |
Table 10.1.5.6.1.3-1 | Notify group dynamic data request |
Table 10.1.5.6.1.4-1 | Notify group dynamic data response |
Table 10.1.5.6.1.5-1 | Cancel group dynamic data subscription request |
Table 10.1.5.6.1.6-1 | Cancel group dynamic data subscription response |
Figure 10.1.5.6.2.1-1 | Subscription for group dynamic data |
Figure 10.1.5.6.2.2-1 | Notification of group dynamic data |
Figure 10.1.5.6.2.3-1 | Cancellation of subscription for group dynamic data |
Figure 10.1.5.6.3.1-1 | Subscription for dynamic data associated with a group |
Figure 10.1.5.6.3.2-1 | Notification of dynamic data associated with a group |
Figure 10.1.5.6.3.3-1 | Cancellation of subscription for dynamic data associated with a group |
Figure 10.1.5.6.4.1-1 | Subscription for dynamic data associated with a group |
Figure 10.1.5.6.4.2-1 | Notification of dynamic data associated with a group |
Figure 10.1.5.6.4.3-1 | Cancellation of subscription for dynamic data associated with a group |
Figure 10.1.7.1-1 | Retrieve functional alias configurations from the functional alias management server |
Figure 10.1.7.2-1 | Subscription for functional alias configurations |
Figure 10.1.7.2-2 | Notification of functional alias configurations |
Table 10.1.7.3-1 | Dynamic data associated with a functional alias |
Table 10.2.2.1-1 | Group creation request |
Table 10.2.2.2-1 | Group creation response |
Table 10.2.2.3-1 | Group regroup request |
Table 10.2.2.4-1 | Group regroup response |
Table 10.2.2.5-1 | Group regroup teardown request |
Table 10.2.2.6-1 | Group regroup teardown response |
Table 10.2.2.7-1 | Group creation notify |
Table 10.2.2.8-1 | Group regroup notify |
Table 10.2.2.9-1 | Group regroup teardown notify |
Table 10.2.2.10-1 | Group regroup teardown notification |
Table 10.2.2.11-1 | Group regroup teardown notification response |
Table 10.2.2.12-1 | Group regroup request |
Table 10.2.2.13-1 | Group regroup response |
Table 10.2.2.14-1 | Group regroup notification |
Table 10.2.2.15-1 | Group regroup notification response |
Table 10.2.2.16-1 | Group information query request |
Table 10.2.2.17-1 | Group information query response |
Table 10.2.2.18-1 | Group membership update request |
Table 10.2.2.19-1 | Group membership update response |
Table 10.2.2.20-1 | Group membership notification |
Table 10.2.2.20-2 | Group membership notification |
Table 10.2.2.21-1 | Group deletion request |
Table 10.2.2.22-1 | Group deletion response |
Table 10.2.2.23-1 | Group deletion notification |
Table 10.2.2.24-1 | Group information provision request |
Table 10.2.2.25-1 | Group information provision response |
Table 10.2.2.26-1 | Group information request |
Table 10.2.2.27-1 | Group information response |
Table 10.2.2.28-1 | Group information subscribe request |
Table 10.2.2.29-1 | Group information subscribe response |
Table 10.2.2.30-1 | Group information notify request |
Table 10.2.2.31-1 | Group information notify response |
Figure 10.2.3-1 | Group creation |
Figure 10.2.4.1-1 | Group regroup for the groups within the same MC system |
Figure 10.2.4.2-1 | Temporary group formation - group regrouping involving multiple MC systems |
Figure 10.2.4.2a-1 | Temporary group tear down within an MC system |
Figure 10.2.4.3-1 | Temporary group tear down |
Figure 10.2.5.2-1 | membership or affiliation list query |
Figure 10.2.6.1-1 | group membership notification |
Figure 10.2.6.2-1 | Group membership update by authorized user |
Figure 10.2.7.2-1 | Primary MC system provides group configuration to partner MC system |
Figure 10.2.7.3-1 | Partner MC system requests group configuration from primary MC system |
Figure 10.2.7.4-1 | Subscription from partner MC system to primary MC system for MC service group configuration |
Figure 10.2.7.5-1 | Notification of group configuration information to partner MC system of MC service group |
Figure 10.2.8-1 | Group deletion |
Figure 10.3.2.2-1 | Pre-established session establishment |
Figure 10.3.2.3-1 | Pre-established session modification |
Figure 10.3.2.4-1 | MC service client within the MC service UE initiated pre-established session release |
Figure 10.3.2.4-2 | MC service server initiated pre-established session release |
Figure 10.6.1-1 | MC service user authentication and registration with Primary MC system, single domain |
Table 10.6.3.2.1-1 | Migration service authorization request |
Table 10.6.3.2.2-1 | Migration service authorization response |
Table 10.6.3.2.3-1 | Migration service de-authorization notification |
Table 10.6.3.2.4-1 | MC service user authorization notification |
Figure 10.6.3.3.1-1 | Service authorization for migration to partner MC system and subsequent service authorization |
Figure 10.6.3.3.2.1-1 | Service de-authorization of migration from partner MC system |
Figure 10.6.3.3.2.2-1 | Service de-authorization of migration from partner MC system |
Table 10.7.2.1-1 | MBMS bearer announcement |
Table 10.7.2.2-1 | MBMS listening status report |
Table 10.7.2.3-1 | MBMS suspension reporting instruction (unicast) |
Table 10.7.2.3-2 | MBMS suspension reporting instruction (multicast) |
Table 10.7.2.4-1 | Discover bearer request |
Table 10.7.2.5-1 | Discover bearer response |
Table 10.7.2.6-1 | Media distribution request |
Table 10.7.2.7-1 | Media distribution response |
Table 10.7.2.10-1 | Media distribution release |
Table 10.7.2.12-1 | Group status notification |
Table 10.7.2.13-1 | MBMS suspension report |
Figure 10.7.3.1.2-1 | Use of pre-established MBMS bearers |
Figure 10.7.3.2-1 | Use of dynamic MBMS bearer establishment |
Figure 10.7.3.3-1 | Switching from MBMS delivery to unicast delivery |
Figure 10.7.3.4.2-1 | Use of MBMS bearer for application level control signalling |
Figure 10.7.3.5.2-1 | MBMS bearer announcement over an MBMS bearer used for application control messages |
Figure 10.7.3.6.2-1 | MBMS bearer quality detection |
Figure 10.7.3.7.2-1 | Two MBMS bearer using overlapping MBSFN areas |
Figure 10.7.3.7.2-2 | Service continuity when moving from one MBSFN to another |
Figure 10.7.3.7.2-3 | Two MBMS bearer using overlapping MBSFN areas with a separate MC application signalling bearer |
Figure 10.7.3.7.3-1 | UE A is moving from a position in MBMS coverage to outside the network coverage passing an area where only unicast is possible |
Figure 10.7.3.7.3-2 | Service continuity over MBMS bearer using UE-to-network relay |
Figure 10.7.3.8.2-1 | MBMS suspension notification from MC service client |
Figure 10.7.3.9.2.1-1 | Multiple server MBMS procedure |
Figure 10.7.3.9.2.2-1 | Multiple server MBMS procedure |
Figure 10.7.3.10.2-1 | MBMS bearer event notification |
Figure 10.7.3.11.2-1 | Application of FEC by the BM-SC |
Figure 10.7.3.11.3-1 | Application of FEC by the MC service server |
Figure 10.7.3.12.2-1 | Header compression by the MC service server |
Figure 10.7.3.12.3-1 | Header compression by the BM-SC |
Table 10.8.2.1-1 | MC service group affiliation request |
Table 10.8.2.2-1 | MC service group affiliation request |
Table 10.8.2.3-1 | MC service group affiliation response |
Table 10.8.2.4-1 | MC service group affiliation response |
Table 10.8.2.6-1 | MC service group de-affiliation request |
Table 10.8.2.7-1 | MC service group de-affiliation request |
Table 10.8.2.8-1 | MC service group de-affiliation response |
Table 10.8.2.9-1 | MC service group de-affiliation response |
Table 10.8.2.11-1 | MC service group affiliation change request |
Table 10.8.2.12-1 | MC service group affiliation change response |
Table 10.8.2.13-1 | MC service group de-affiliation notification |
Table 10.8.2.14-1 | Notify group dynamic data request |
Figure 10.8.3.1-1 | MC service group affiliation procedure |
Figure 10.8.3.2.2-1 | Affiliation for an MC service group defined in partner MC system where topology hiding is not required |
Figure 10.8.3.2a.2-1 | Group affiliation to an MCservice group defined in partner MC system using topology hiding |
Figure 10.8.4.2-1 | MC service group de-affiliation procedure |
Figure 10.8.4.3-1 | De-affiliation from an MC service group defined in partner MC system |
Figure 10.8.4.4-1 | MC service server initiated group de-affiliation procedure |
Figure 10.8.4.5-1 | MC service server initiated group de-affiliation from group in partner system procedure |
Figure 10.8.5.1.1-1 | Remotely change MC service group affiliation - mandatory mode |
Figure 10.8.5.1.2-1 | Remotely change MC service group affiliation - negotiated mode |
Figure 10.8.5.2.1-1 | Remote change MC service group affiliation defined in partner MC system - mandatory mode |
Table 10.9.2.1-1 | Location reporting configuration |
Table 10.9.2.2-1 | Location information report |
Table 10.9.2.2-2 | Location information report (LMS - LMC) |
Table 10.9.2.2-3 | Location information report (LMS - MC service server) |
Table 10.9.2.2-4 | Location information report (LMS - LMS) |
Table 10.9.2.3-1 | Location information request (MC service server to location management server) |
Table 10.9.2.3-2 | Location information request (Location management server to location management client) |
Table 10.9.2.3-3 | Location information request (Location management client to location management server) |
Table 10.9.2.3-4 | Location information request (Location management server to location management server) |
Table 10.9.2.4-1 | Location reporting trigger |
Table 10.9.2.4a-1 | Location reporting trigger cancel |
Table 10.9.2.5-1 | Location information subscription request (MC service server - LMS) |
Table 10.9.2.5-2 | Location information subscription request (LMC - LMS) |
Table 10.9.2.5-3 | Location information subscription request (LMS - LMS) |
Table 10.9.2.6-1 | Location information subscription response |
Table 10.9.2.7-1 | Location information notification (LMS to MC service server) |
Table 10.9.2.7-2 | Location information notification (LMS to LMC) |
Table 10.9.2.7-3 | Location information notification (LMS to LMS) |
Table 10.9.2.8-1 | Location information cancel subscription request (MC service server to location management server) |
Table 10.9.2.8-2 | Location information cancel subscription request (Location management client to location management server) |
Table 10.9.2.8-3 | Location information cancel subscription request (Location management server to location management server) |
Table 10.9.2.9-1 | Location information cancel subscription response (Location management server to MC service server) |
Table 10.9.2.9-2 | Location information cancel subscription response (Location management server to location management client) |
Table 10.9.2.9-3 | Location information cancel subscription response (Location management server to location management server) |
Table 10.9.2.11-1 | Location information history status request (LMC - LMS) |
Table 10.9.2.11-2 | Location information history status request (LMS - LMC) |
Table 10.9.2.11-3 | Location information history status request (MC service server - LMS) |
Table 10.9.2.12-1 | Location information history status report (LMC - LMS) |
Table 10.9.2.12-2 | Location information history status report (LMS - LMC) |
Table 10.9.2.12-3 | Location information history status report (LMS - MC service server) |
Table 10.9.2.13-1 | Location information history request (LMC - LMS) |
Table 10.9.2.13-2 | Location information history request (LMS - LMC) |
Table 10.9.2.13-3 | Location information history request (MC service server - LMS) |
Table 10.9.2.14-1 | Location information history report (LMC - LMS) |
Table 10.9.2.14-2 | Location information history report (LMS - LMC) |
Table 10.9.2.14-3 | Location information history report (LMS - MC service server) |
Table 10.9.2.15-1 | Location information history cancel request (LMC - LMS) |
Table 10.9.2.15-2 | Location information history cancel request (LMS - LMC) |
Table 10.9.2.15-3 | Location information history cancel request (MC service server - LMS) |
Table 10.9.2.16-1 | Location information history cancel response (LMC - LMS) |
Table 10.9.2.16-2 | Location information history cancel response (LMS - LMC) |
Table 10.9.2.16-3 | Location information history cancel response (LMS - MC service server) |
Table 10.9.2.17-1 | Location reporting temporary configuration request |
Table 10.9.2.18-1 | Location reporting temporary configuration response |
Table 10.9.2.19-1 | Restrict location information dissemination request information elements |
Table 10.9.2.20-1 | Restrict location information dissemination response information elements |
Table 10.9.2.21-1 | Restrict location information dissemination notification information elements (LMS to LMC) |
Table 10.9.2.21-2 | Restrict location information dissemination notification information elements (LMS to MC service server) |
Table 10.9.2.22-1 | Location reporting trigger override indication |
Table 10.9.2.23-1 | Location reporting trigger override indication |
Figure 10.9.3.1-1 | Event-triggered location reporting procedure |
Figure 10.9.3.2-1 | On-demand location information reporting procedure |
Figure 10.9.3.3-1 | Client-triggered location reporting procedure |
Figure 10.9.3.4-1 | Event-triggered location reporting cancel procedure |
Figure 10.9.3.4a-1 | Client-triggered location reporting cancel procedure |
Figure 10.9.3.4b-1 | Client-triggered location reporting cancel procedure targeting MC service group(s) |
Figure 10.9.3.5-1 | Location information subscription request procedure |
Figure 10.9.3.6.1-1 | Event-trigger usage of location information procedure |
Figure 10.9.3.6.2-1 | On-demand usage of location information procedure |
Figure 10.9.3.7-1 | Location information cancel subscription request procedure |
Figure 10.9.3.8.1-1 | One-time location information report for shared functional alias |
Figure 10.9.3.8.2-1 | Periodic location information report for shared functional alias |
Figure 10.9.3.8.3-1 | Periodic location information report cancellation for shared functional alias |
Figure 10.9.3.9.2.1-1 | On-demand based usage of report location history procedure (LMC - LMS) |
Figure 10.9.3.9.2.2-1 | On-demand based usage of report location history procedure |
Figure 10.9.3.9.3.1-1 | Status location history reporting procedure (LMC - LMS) |
Figure 10.9.3.9.3.2-1 | On-demand based usage of status location history reporting procedure (LMS - LMC) |
Figure 10.9.3.9.3.3-1 | On-demand based usage of status location history reporting procedure |
Figure 10.9.3.9.4.2-1 | Cancel location history reporting procedure (LMS - LMC) |
Figure 10.9.3.9.4.3-1 | Cancel location history reporting procedure |
Figure 10.9.3.10.2-1 | On-demand request of location information procedure |
Figure 10.9.3.10.3-1 | Event-triggered location information notification procedure |
Figure 10.9.3.10.4-1 | Location information subscription procedure |
Figure 10.9.3.10.5-1 | Location information cancel subscription procedure |
Figure 10.9.3.10.6-1 | Location reporting temporary configuration procedure |
Figure 10.9.3.11-1 | Restrict the location information dissemination procedure |
Figure 10.9.3.12.2-1 | Trigger override procedure |
Figure 10.9.3.12.3-1 | Cancel trigger override procedure |
Table 10.10.1.1A.1-1 | MC service emergency alert request information elements |
Table 10.10.1.1A.2-1 | MC service emergency alert response information elements |
Table 10.10.1.1A.3-1 | MC service emergency alert cancel request information elements |
Table 10.10.1.1A.4-1 | MC service emergency alert cancel response information elements |
Table 10.10.1.1A.5-1 | MC service emergency alert area notification information elements |
Figure 10.10.1.2.1.2-1 | MC service group emergency alert |
Figure 10.10.1.2.1.3-1 | MC service individual emergency alert |
Figure 10.10.1.2.2.2-1 | MC service group emergency alert cancel |
Figure 10.10.1.2.2.3-1 | MC service individual emergency alert cancel |
Figure 10.10.1.2.3-1 | Entering MC service emergency alert area |
Figure 10.10.1.2.4-1 | Leaving MC service emergency alert area |
Table 10.10.2.1A.1-1 | MC service emergency alert announcement information elements |
Table 10.10.2.1A.2-1 | MC service emergency alert cancel announcement information elements |
Figure 10.10.2.2.1-1 | Emergency alert initiation |
Figure 10.10.2.2.2-1 | Emergency alert cancel |
Table 10.10.3.2.1-1 | Ad hoc group emergency alert request information elements |
Table 10.10.3.2.2-1 | Ad hoc group emergency alert request information elements |
Table 10.10.3.2.2a-1 | Ad hoc group emergency alert request return information elements |
Table 10.10.3.2.3-1 | Ad hoc group emergency alert response information elements |
Table 10.10.3.2.4-1 | Ad hoc group emergency alert cancel request information elements |
Table 10.10.3.2.4a-1 | Ad hoc group emergency alert cancel request return information elements |
Table 10.10.3.2.5-1 | Ad hoc group emergency alert cancel response information elements |
Table 10.10.3.2.6-1 | Ad hoc group emergency alert participants list notification information elements |
Table 10.10.3.2.7-1 | Ad hoc group emergency alert get userlist request |
Table 10.10.3.2.8-1 | Ad hoc group emergency alert get userlist response |
Table 10.10.3.2.9-1 | Ad hoc group emergency alert user add notification |
Table 10.10.3.2.10-1 | Ad hoc group emergency alert user remove notification |
Table 10.10.3.2.11-1 | Ad hoc group emergency alert notify |
Table 10.10.3.2.12-1 | Ad hoc group emergency alert modify request information elements |
Table 10.10.3.2.12a-1 | Ad hoc group emergency alert modify request return information elements |
Table 10.10.3.2.13-1 | Ad hoc group emergency alert modify response information elements |
Figure 10.10.3.3.1-1 | Ad hoc group emergency alert initiation |
Figure 10.10.3.3.2-1 | Ad hoc group emergency alert cancel |
Figure 10.10.3.3.3-1 | Entering an ongoing ad hoc group emergency alert |
Figure 10.10.3.3.4-1 | Leaving an ad hoc group emergency alert |
Figure 10.10.3.3.5-1 | Modifying the criteria for determining the participants during an ongoing ad hoc group emergency alert |
Figure 10.10.3.4.1-1 | Ad hoc group emergency alert initiation between multiple MC systems |
Figure 10.10.3.4.2-1 | Updating the participant list of an ongoing ad hoc group emergency alert between multiple MC systems |
Figure 10.10.3.4.3-1 | Ad hoc group emergency alert cancel between multiple MC systems |
Figure 10.10.3.4.4-1 | Modifying the criteria for determining the participants during an ongoing ad hoc group emergency alert between multiple MC systems |
Figure 10.11.2-1 | Resource request at session establishment - SIP core based |
Figure 10.11.2a.2-1 | Resource request at session establishment - MC service server based |
Figure 10.11.3-1 | Bearer modification request |
Figure 10.11.5.2-1 | Resource request including priority sharing information |
Figure 10.11.6.2-1 | Request for resources for transmission control and media plane |
Table 10.12.1.1-1 | MC priority request |
Figure 10.12.3-1 | Priority arbitration between multiple MC service servers |
Table 10.13.2.1-1 | Active functional alias information user query request |
Table 10.13.2.1a-1 | Active functional alias information usage query request |
Table 10.13.2.2-1 | Active functional alias information user query response |
Table 10.13.2.2a-1 | Active functional alias information usage query response |
Table 10.13.2.3-1 | Functional alias activation request |
Table 10.13.2.4-1 | Functional alias activation response |
Table 10.13.2.5-1 | Functional alias de-activation request |
Table 10.13.2.6-1 | Functional alias de-activation response |
Table 10.13.2.7-1 | Functional alias status notification |
Table 10.13.2.8-1 | Functional alias take over request |
Table 10.13.2.9-1 | Functional alias take over response |
Table 10.13.2.10-1 | Functional alias revoke notification |
Table 10.13.2.11-1 | Subscribe functional alias request |
Table 10.13.2.12-1 | Subscribe functional alias response |
Table 10.13.2.13-1 | Notify functional alias request |
Table 10.13.2.14-1 | Notify functional alias response |
Table 10.13.2.15-1 | Unsubscribe functional alias request |
Table 10.13.2.16-1 | Unsubscribe functional alias response |
Table 10.13.2.17-1 | Functional alias to group binding request |
Table 10.13.2.18-1 | Functional alias to group binding response |
Table 10.13.2.19-1 | Functional alias to group unbinding request |
Table 10.13.2.20-1 | Functional alias to group unbinding response |
Figure 10.13.3-1 | Active functional alias list query for the user |
Figure 10.13.4-1 | Functional alias activation procedure within an MC system |
Figure 10.13.5-1 | Functional alias de-activation procedure within an MC system |
Figure 10.13.6-1 | Functional alias taking over procedure within an MC system |
Figure 10.13.7-1 | Query of usage of the active functional alias(es) |
Figure 10.13.8-1 | Automatic functional alias activation within an MC system |
Figure 10.13.9-1 | Automatic functional alias deactivation within an MC system |
Figure 10.13.10.2-1 | Subscription for functional alias |
Figure 10.13.10.3-1 | Notification for the functional alias |
Figure 10.13.10.4-1 | Unsubscription for functional alias |
Figure 10.13.11.2-1 | Functional alias to group binding procedure |
Figure 10.13.11.3-1 | Functional alias to group unbinding procedure |
Figure 10.14.2.2-1 | Call to target in interconnected MC system |
Figure 10.14.3.2-1 | Enforcement of local configuration with call originated in partner MC system of MC service group |
Figure 10.14.3.3-1 | Enforcement of local configuration where group call request is received from primary MC system of MC service group |
Figure 10.14.4.2-1 | Media replication in partner MC system of MC service group |
Table 10.15.2.1-1 | Preconfigured regroup request information elements |
Table 10.15.2.2-1 | Preconfigured regroup request information elements |
Table 10.15.2.3-1 | Preconfigured regroup request information elements |
Table 10.15.2.4-1 | Preconfigured regroup response information elements |
Table 10.15.2.5-1 | Preconfigured regroup response information elements |
Table 10.15.2.6-1 | Preconfigured regroup response information elements |
Table 10.15.2.7-1 | Preconfigured regroup cancel request information elements |
Table 10.15.2.8-1 | Preconfigured regroup cancel request information elements |
Table 10.15.2.9-1 | Preconfigured regroup cancel request information elements |
Table 10.15.2.10-1 | Preconfigured regroup cancel response information elements |
Table 10.15.2.11-1 | Preconfigured regroup cancel response information elements |
Table 10.15.2.12-1 | Preconfigured regroup cancel response information elements |
Table 10.15.2.13-1 | Preconfigured regroup reject information elements |
Table 10.15.2.14-1 | Preconfigured regroup reject information elements |
Table 10.15.2.15-1 | Preconfigured user regroup remove request information elements |
Table 10.15.2.16-1 | Preconfigured user regroup remove response information elements |
Table 10.15.2.17-1 | Preconfigured regroup request return information elements |
Figure 10.15.3.2.1-1 | Regroup procedure using preconfigured group in a single MC system |
Figure 10.15.3.2.2-1 | User regroup procedure using preconfigured group in a single MC system |
Figure 10.15.3.2.3-1 | Cancel preconfigured regroup procedure in a single MC system |
Figure 10.15.3.3.1-1 | Group regroup procedure using preconfigured group in multiple MC systems |
Figure 10.15.3.3.2-1 | User regroup procedure using preconfigured group in multiple MC systems |
Figure 10.15.3.3.3-1 | Cancel preconfigured regroup procedure in multiple MC systems |
Figure 10.15.3.3.4-1 | Regroup rejection using preconfigured group in multiple MC systems |
Figure 10.15.3.4.1-1 | Procedure to add a newly affiliated user to a preconfigured group regroup |
Figure 10.15.3.4.2-1 | Procedure to update the MC service ID list |
Figure 10.15.3.4.3-1 | Procedure for communication request on MC service group during an in-progress group regroup |
Figure 10.15.3.4.4-1 | Procedure for communication request to regroup group after the regrouping cancellation |
Figure 10.16.2.2-1 | Migration to partner MC system during an ongoing group call |
Table 10.16.3.2.1-1 | MC service functional alias resolution request information elements |
Table 10.16.3.2.2-1 | MC service functional alias resolution response information elements |
Figure 10.16.3.3-1 | Private call setup in automatic commencement mode, users in multiple MC systems |
Figure 10.16.4.2-1 | Migration during ongoing private communication |
Table 10.16.5.2-1 | Private call redirection |
Figure 10.16.5.3-1 | MC private call towards a migrated MC service user |
Table 10.16.6.2.1-1 | Ad hoc group call redirection notify |
Figure 10.16.6.3-1 | Ad hoc group call towards migrated MC service users |
Table 10.16.7.2.1-1 | Ad hoc group call redirection notify |
Figure 10.16.7.3-1 | Migration during ongoing ad hoc group call based on participants list |
Figure 10.16.7.4-1 | Migration during ongoing ad hoc group call based on criteria |
Table 10.17.2.1-1 | ACM data notification |
Table 10.17.2.2-1 | Get ACM data request |
Table 10.17.2.3-1 | Get ACM data response |
Table 10.17.2.4-1 | Group membership update request |
Table 10.17.2.5-1 | Group membership update response |
Table 10.17.2.6-1 | Process indication |
Table 10.17.2.7-1 | Interconnection group information provision request |
Table 10.17.2.8-1 | Interconnection group identity provision response |
Table 10.17.2.9-1 | Add user configuration request |
Table 10.17.2.10-1 | Add user configuration response |
Table 10.17.2.11-1 | Remove user configuration request |
Table 10.17.2.12-1 | Remove user configuration response |
Table 10.17.2.13-1 | Update MC service UE initial configuration request |
Table 10.17.2.14-1 | Update MC service UE initial configuration response |
Table 10.17.2.15-1 | MC service user profile update request |
Table 10.17.2.16-1 | MC service user profile update response |
Figure 10.17.3.1.2-1 | Pending requests Procedure |
Figure 10.17.3.2.2-1 | Automation performed by ACM server |
Figure 10.17.3.2.3-1 | Automation performed by an automated ACM client |
Figure 10.17.4.1.2.1-1 | Group membership update by authorized user from a primary MC system |
Figure 10.17.4.2.2-1 | Providing interconnection MC service group ID(s) to partner MC system |
Figure 10.17.5.2-1 | Add user configuration request in partner MC system |
Figure 10.17.5.3-1 | Remove user configuration request from a partner MC system |
Figure 10.17.6.2-1 | Update MC service UE initial configuration |
Figure 10.17.7.2-1 | MC service user profile update |
Figure 10.18.1.1-1 | The relationship of MC service user, MCRec ID and Recording admin and replay service user profile |
Figure 10.18.1.2-1 | Recording admin UE configuration time sequence and associated configuration data |
Figure 10.18.1.3-1 | Replay UE configuration time sequence and associated configuration data |
Table 10.18.1.4.1-1 | Get recording admin and replay service user profile request |
Table 10.18.1.4.2-1 | Get recording admin and replay service user profile response |
Table 10.18.1.4.3-1 | Notification for recording admin and replay service user profile data update |
Table 10.18.1.4.4-1 | Get updated recording admin and replay service user profile data request |
Table 10.18.1.4.5-1 | Get updated recording admin and replay service user profile data response |
Figure 10.18.1.5.1-1 | Recording admin and/or replay user obtains the user profile from the network |
Figure 10.18.1.5.2-1 | Recording admin and/or replay service user receives updated user profile data from the CMS |
Figure 10.18.2.1-1 | Store target group configuration at group management server |
Figure 10.18.2.2-1 | Update target MC service user profile data to the CMS |
Figure 10.18.3.2-1 | Recording procedure for a target MC service user |
Figure 10.18.3.3-1 | Procedure for recording communication sessions of an MC service group |
Figure 10.18.4.2-1 | Procedure for fetching a recording from a recording server |
Figure 11.2.0-1 | Functional architecture |
Figure 11.2.0-2 | Simultaneous multiple MC gateway UE use by a single non-3GPP device |
Figure 11.2.1-1 | Functional model of MC gateway UE application plane with MC client hosted in the non- 3GPP device |
Figure 11.2.1-2 | Functional model of MC gateway UE signalling plane with MC client hosted in the non- 3GPP device |
Figure 11.2.1-3 | Functional model of MC gateway UE application plane with MC client hosted in the MC gateway UE |
Figure 11.3.2-1 | IMC per MC service client |
Figure 11.3.3-1 | Sharing MC gateway UE's IMC for non-3GPP devices which cannot host a client |
Table 11.5.2.2.1-1 | MC GW location reporting configuration |
Table 11.5.2.2.2-1 | MC GW location information report |
Table 11.5.2.2.3-1 | MC GW location information request |
Figure 11.5.2.3.1-1 | Event-triggered location reporting procedure |
Figure 11.5.2.3.2-1 | On-demand location reporting procedure |
Figure 11.5.2.3.3-1 | On-demand location reporting procedure |
Table 11.5.3.2.1-1 | MC GW MBMS bearer announcement |
Table 11.5.3.2.2-1 | MC GW MBMS listening status report |
Table 11.5.3.2.3-1 | MC GW MapGroupToBearer request |
Table 11.5.3.2.4-1 | MC GW MapGroupToBearer response |
Table 11.5.3.2.5-1 | MC GW MapGroupToBearer response |
Table 11.5.3.2.6-1 | MC GW MBMS bearer suspension indication |
Table 11.5.3.2.7-1 | MC GW UnMapGroupToBearer request |
Table 11.5.3.2.8-1 | MC GW UnMapGroupToBearer response |
Figure 11.5.3.3.1-1 | Handling of MBMS bearer announcement |
Figure 11.5.3.3.2-1 | Handling of MapGroupToBearer message |
Figure 11.5.3.3.2A-1 | Handling of UnmapGroupFromBearer message |
Figure 11.5.3.3.3-1 | MBMS bearer suspension notification |
Figure 11.5.3.3.4-1 | Reporting MBMS bearer quality |
Table A.4-1 | Common group configuration data (on and off network) |
Table A.4-2 | Common group configuration data (on-network) |
Table A.4-3 | Common group configuration data (off-network) |
Table A.6-1 | Initial MC service UE configuration data (on-network) |
Table A.8-1 | location user profile data (on and off network) |
Table A.9-1 | MC service user profile configurations for authorisation of ACM (on-network) |
Table A.10-1 | Initial recording admin UE and/or replay UE configuration data (on-network) |
Table A.11-1 | Recording admin and/or replay service user profile configuration data (on-network) |
Figure B.1-1 | Service continuity from on-network to UE-to-network relay |
Figure B.1-2 | Service continuity when UE switches from on-network MCPTT service to UE-to-network relay MCPTT service |
Figure C.1-1 | Types of application priorities in the MC system |
Figure E.2-1 | MC client IP address relationship |
Figure E.3-1 | non-3GPP device uses MC gateway UE's IP address |