3gpp tr ab cde
Mission Critical Data over LTE
Yüklə 0,91 Mb.
|
- Bu səhifədəki naviqasiya:
- Common functional architecture to support mission critical services
Mission Critical Data over LTESummary based on the input provided by the UK Home Office in SP-170749.
Introduction Clause 6.1 above explains the relationship in Rel-14 between TS 22.179 (MCPTT), TS 22.280 (MCCoRe), TS 22.281 (MCVideo) and TS 22.282 (MCData). This clause deals more specifically with TS 22.282, which provides the MCPTT requirements applicable to MC Data, and the corresponding Stage 2 in 23.282. With the progress of Mission Critical Push To Talk (MCPTT) it was identified that there remained a need for other Mission Critical Services which could also make use of the security, identity obfuscation and quality of service handling which serve as the basis for MCPTT. Mission Critical Data (MCData) is the Work Item addressing handling of data services within that Mission Critical framework. Overview of TS 22.282 on MCPTT Data MCData in Release 14 is defined to include a short message service and a file transfer service with conversation management and disposition reporting. There is also an enhanced status reporting capability. Other data services initially envisaged at stage 1 have been postponed to Release 15. The Short message Distribution Service (SDS) can deliver messages over the signalling channel or over a media bearer. SDS over media bearer can be standalone where the media bearer is set up for the purpose of delivering one message only and then disconnected afterwards or the media bearer can be established as a session for a group to carry multiple messages among group members. As a short message service, there is no pre-check for permission to transmit. The protocol used will handle any size of message so no segmentation or concatenation is required, but a configurable size limit is introduced to protect against unlimited and uncontrolled permission to transmit. The File Distribution service (FD) can be: - session based when all recipients are required to make mandatory download; or - http upload and temporary store in the controlling MCData server followed by distribution of notification of the file availability for the target recipients. This way distribution control is managed and the recipient clients can manage their own reception. There is also provision for mandatory download with the http method. Mandatory download is indicated from the sending user to the receiving user(s). SDS and FD can utilize a combined conversation management capability for conversation tracking and grouping. SDS and FD also both use a disposition mechanism to indicate the status of delivery of the content.
Summary based on the input provided by Huawei in SP-170766.
See clause 6.1 above on re-organizing the MCPTT documents. The main objective of the MCImp-MC_ARCH work item is to specify a common functional architecture for all mission critical services to support on-network and off-network operations. This common functional architecture includes the common services core functions and certain generic mechanisms (e.g. affiliation) for MCPTT, MCVideo and MCData services to be uniformly developed. This work item enables the re-use of the common services by other mission critical services not limited only to MCPTT. The common functional architecture to support mission critical services can be used for public safety applications and also for general commercial applications e.g. utility companies and railways. The MCImp-MC_ARCH work item is applicable for two or more mission critical services and consists of architectural requirements, common functional models for on network and off network, identities, deployment models, procedures and information flows and configurations corresponding to UE, user profile, group and service. The common functional architecture to support MC services utilizes aspects of the IMS architecture defined in TS 23.228, the Proximity-based Services (ProSe) architecture defined in TS 23.303, the Group Communication System Enablers for LTE (GCSE_LTE) architecture defined in TS 23.468 and the PS-PS access transfer procedures defined in TS 23.237. The MC service UE primarily obtains access to a MC service via E-UTRAN, using the EPS architecture defined in TS 23.401. Certain MC service functions such as dispatch and administrative functions can be supported using either MC service UEs in E-UTRAN or using MC service UEs via non-3GPP access networks. These aspects are fully compliant with the MCPTT architecture specified for Release 13 in TS 23.179. The common functional architecture provides for common functionalities (common services core) to support MC services (MCPTT service, MCVideo service and MCData service). The key functionalities supported by common services core are:
The generic mechanisms specified are applicable to at least two or more MC services. The generic mechanisms are documented in TS 23.280 for purpose of reducing duplication of procedures for each MC service. The following generic mechanisms are specified: - Use of UE-to-network relay service to allow ProSe UE to UE communications to support off-network operations for MCPTT service, MCVideo service and MCData service. Support for restricting the relayed group communication on a per group basis. (Implemented only for MCPTT service in Release 14) - Affiliation to groups, affiliation to groups defined in partner MC system, de-affiliation from groups, de-affiliation from groups defined in partner MC system and remote change of a MC service user's affiliation to groups defined primary or partner MC systems by authorized users. The groups may be enabled for any combination of MCPTT service, MCVideo service and MCData service communications. - On-network and off-network emergency alert initiation and emergency state cancel for MCVideo service and MCData service communications.
|