hash
stringlengths 32
32
| doc_id
stringlengths 5
12
| section
stringlengths 5
1.47k
| content
stringlengths 0
6.67M
|
|---|---|---|---|
72a4e55cbcd7a63aa54799710b138216
|
22.156
|
8.2 Requirements
| |
72a4e55cbcd7a63aa54799710b138216
|
22.156
|
8.2.1 Localized mobile metaverse service
|
[R-8.2.1-001] The 5G system shall be able to collect charging information for the actions related to spatial anchors, where a third party creates, deletes, or modifies a spatial anchor or associated service information.
NOTE: It is assumed that exposure of network anchors and associated service information can be a service provided by a network operator to third parties.
[R-8.2.1-002] The 5G system shall support the collection of charging information associated with the exposure of a spatial map or derived localization information to authorized third parties.
[R-8.2.1-003] The 5G system shall support the collection of charging information associated with the production or modification of a spatial map on behalf of an authorized third party.
[R-8.2.1-004] The 5G system shall support the collection of charging information associated with exposing spatial location service information to authorized third parties.
[R-8.2.1-005] The 5G system shall be able to collect charging information associated with distribution of third party mobile metaverse media to one or more subscribers.
|
72a4e55cbcd7a63aa54799710b138216
|
22.156
|
8.2.2 Avatar-based real-time communication
|
[R-8.2.2-001] The 5G system shall support collection of charging information associated with initiating and terminating avatar call.
[R-8.2.2-002] The 5G system shall be able to collect charging information for transcoding services associated with avatar call.
|
72a4e55cbcd7a63aa54799710b138216
|
22.156
|
8.2.3 Digital asset management
|
[R-8.2.3-001] The 5G system shall be able to collect charging information per UE or per application, related to the use of digital assets associated with a user (e.g., typically a human user with a certain subscription). [R-8.2.3-002] The 5G system shall be able to collect charging information per UE for managing the digital assets associated with a user (e.g., typically a human user with a certain subscription) or a third party. NOTE: A third party who has digital assets could be an enterprise customer having service level agreement with the operator. Annex A (informative): Mobile metaverse services A.1 Introduction This document defines the "mobile metaverse" as the user experience enabled by the 5G system of interactive and/or immersive XR media, including haptic media. For clarity and unambiguity with respect to many divergent technical and commercial developments, this document avoids the use of the term "metaverse" without qualification with the term "mobile". This annex provides background information for the present document and further explanation of the term mobile metaverse, and the services that it enables. The term mobile metaverse implies the combination of various technologies to fuse physical and digital worlds, widely impacting society and the economy. Users will access these mobile metaverse services with devices for interaction with XR media and sensors, enabled by mobile telecommunication standards. Mobile metaverse services are expected to be provided via many and diverse service providers, each catering to different customers, companies and communities. An entertainment company might provide one mobile metaverse service for consumers such as a virtual theme park, while offering a separate mobile metaverse service to its employees. Some providers may specialize in interactive tools to create content, while others present that content. In general, mobile metaverse services can be divided into three general categories: industrial, enterprise and consumer mobile metaverse services. There are commonalities among these categories. These mobile metaverse services will apply across these domains to varying degrees, sharing technologies, devices and interfaces, and functionalities described in this document. Ultimately, mobile metaverse services will be defined by the applications they enable and the business models they adopt. Besides "experiencing" virtual world and/or augmented real world media as a passive consumer (where the media is read-only), mobile metaverse services also can enable interaction, the user can "create" and even "control" elements of the media. Depending on the mobile metaverse service, the consequence of user interaction could be experienced by other users. As discussed below, in some cases, user interaction may result even in changes to the real world, through 'actuation' (remote control mechanisms) as discussed in clause A.4. Mobile metaverse services face technical challenges specific to the media and interactions they offer to users, in the context of mobile networks. Some of these technical challenges are addressed by mobile telecommunications standards, of which this document is a contribution. Another set of challenges are not technical in nature, such as regulatory and safety implications, only some of which are discussed in the present document. Other technical and non-technical challenges are expected to be addressed separately depending on the target environment/vertical. A.2 Consumer mobile metaverse services There has been some initial development of commercial consumer-oriented mobile metaverse services, specifically in metaverse gaming and VR social media 'virtual worlds'. Mobile metaverse consumer services considered during the study of mobile metaverse services relate to the following use cases: - Attending (live) VR events (sports, gaming, concerts, etc.) either as spectator or performer, including while moving / commuting; - Virtual shopping or visit experience (tourism, real estate, etc.); - Presentation of AR content on a virtual screen, e.g., a feature length movie; - Interaction with AR content in a location-aware manner, offering spatial localization and mapping to support applications generating AR content for enhanced localized experiences (e.g., in museums, shopping malls); - Situation awareness about the user's physical surroundings, while walking or driving; - Experience immersive communications with other entities - digital representations of users or application-generated content, including customer support services, by leveraging avatars, digital assets and wallets. A.3 Enterprise mobile metaverse services Remote working has driven demand for better collaboration and communication tools, and thanks to extended reality (XR) and virtual reality (VR) technologies, many of those tools contribute to the enterprise metaverse. The enterprise mobile metaverse will eventually envelop the core productivity applications that make business function, e.g., as a digital drafting tool for architecture and engineering, and training sessions via AR and/or VR. Eventually, the enterprise and industrial mobile metaverses will interlink, merging the IT systems in office branches with the Operational Technology (OT) systems of the shop floor. Main mobile metaverse enterprise services considered during the study of mobile metaverse services relate to the following use cases: - XR-enabled collaborative and concurrent engineering based on geospatial digital twins (and avatars), for research & prototyping, visual testing & simulation, planning & optimisation, which can further be used for training - Virtual showrooms, products or stores; - Interaction with AR content in a location-aware manner, e.g., creating spatial anchors and discovery of them for AR content enhanced in-store shopping experiences; A.4 Industrial mobile metaverse services Industrial mobile metaverse services are expected to provide cost, productivity, safety and flexibility gains. In particular, industrial OT systems begin to support mobile services that include XR media for monitoring and analysis, and also for control of operations through the digital orchestration of robot fleets or user-guided remote operations. Industrial users will gain the ability to visualize and reconfigure their operations, e.g., in response to changing supply and demand or disruptions. By fusing digital and physical realities, the digital twin has begun to transform many industries. Seaports have begun using digital twins to track every container on their docks. Aerospace companies design and build engines and fuselages virtually to simulate how an aircraft will fly and perform. Many new factories exist just as much digitally, as data and virtual representation, as they do in the physical world. This kind of mobile metaverse service aims at control and awareness of operations down to the smallest detail. Some of the mobile metaverse service enabler requirements support digital twin applications. Main mobile metaverse industrial services considered during the study of mobile metaverse services relate to the following use cases: - Remote critical health care, including surgery and treatment; - AR/VR based tele-operation of a remote device or vehicle (e.g., driving). A.5 Common aspects Common enablers associated with mobile metaverse services are virtual, augmented, mixed and other media (expressed collectively as extended reality, XR.) Whilst these are essential to the realization of the immersive experience of mobile metaverse services, they are not the only enabling functionalities. This document does not focus on XR media and media services per se, but rather identifies requirements for complementary enablers common to all mobile metaverses services, including: - Enabling localized (i.e., location-aware) mobile metaverse services by considering the essential mobility aspect of 5G connectivity, and collection and exposure of sensor data or 'results of processed sensor data' as needed by mobile metaverse services to integrate media into an immersive user's experience and expectations; - Enhancing real-time communications, including over IMS, with avatar-based capabilities, thus allowing more immersiveness in virtual reality, augmented reality, etc. user experiences; - Enhancing XR media delivery to make it possible to support user experience of multiple services simultaneously; - Securely storing, exposing and managing digital assets. Other key enablers of the metaverse implied by some immersive experiences relate to digital twins, defined in this document as "a real-time representation of physical assets in a digital world". With respect to the metaverse, “geospatial” digital twins relate to the concept of adding geospatial information to a digital twin, such as 3D models, precise location and temporal information – enabling for example holographic-type of object animation. The value proposition of geospatial Digital twins is about enabling immersive user experience, collaboration and simulations that are very close to what to expect in the real world by all 3 categories of mobile metaverse services. It is foreseen that additional functionalities will be defined in the future to provide capabilities to better offer and operate mobile metaverse services. Annex B (informative): The EU Digital Identity Wallet Initiative B.1 Overview This annex provides an example of a framework in which a digital asset management services can enable a diverse set of activity for individuals, including health care, commerce, e-government and any activity in which exchange of official documents is essential. This annex does not imply that the digital asset management capabilities specified in the present document can serve or fulfill the EU Digital Identity Wallet initiative goals, though this is not excluded. Rather, this annex provides an overview of the emergence of digital asset management as an essential means to act efficiently and effectively in an increasingly large set of activities. B.2 The Initiative The European Commission intends to establish a sovereign digital/digital identity as part of its digital transformation strategy [11]. While the digital wallet initiative is specific to Europe, the ideas behind it could be generally applicable. That is, to encourage and ease e-commerce, e-government and provide users with control over how their data is accessed, a digital wallet approach could have applicability and value in a broader international context. This digital identity [11] will allow by 2030 the citizens of the union to authenticate themselves to the main public services (or to some services of non-public companies), using a "wallet". This wallet will be an application that will store (in a secure way) a certain number of data and certified documents (identity card, driving license, certificates of personal qualities - like the majority -) in order to share them with the relevant services (e.g., school registration) securely. These solutions are meant to be compatible in all European countries. “Every time an App or website asks us to create a new digital identity or to easily log on via a big platform, we have no idea what happens to our data in reality. That is why the Commission will propose a secure European e-identity. One that we trust and that any citizen can use anywhere in Europe to do anything from paying your taxes to renting a bicycle. A technology where we can control ourselves what data is used and how." [6] The following indented text is a summary of a discussion of "European Digital Identity" [11]. The EU Digital ID Wallet is intended to allow European citizens to safely save their documents and personal information in a manner that complies with privacy regulations, as well as to give the data owners full control how the data is used (who can access it), and to track how it has been used. The information stored in the wallet could have general utility in many circumstances, even outside of the country in which the information was issued. Examples given are driver's licenses, medical records or certification such as university degree titles. It is acknowledged that people need to establish their identity in many ways. This process is currently complex, as each activity requires different credentials and as the form of credentials vary, identification requires different process. Having a single digital identity wallet will simplify these processes. The goal of the program is to bring the following benefits: - To support the ability of every person eligible for a national ID card to have a digital identity that is recognized anywhere in the EU; - To provide a simple and safe way to control how much information you want to hsare with services that require the sharing of information; - To allow mobile phone apps and other devices to support a means to - provide identity services on- and off-line; - store and exchange information provided by governments, e.g., name, surname, date of birth, nationality; - to use information as confirmation ofthe right to reside, work, or study in a particular member state. Today only 60% of the EU population in 14 Member States are able to use their national electronic ID (eID) beyond their own country. Only 14% of key public service providers across all Member states allow cross-border authenticaiton with an eID system, e.g., to prove a person's identity as part of authentication with a service accessed by means of the Internet without the need of a password.There are many situations where such identity information is needed, mainly during interaction with the government. For example, filing tax returns, changing one's address. Many other activities require identification, e.g., opening a bank account, renting a car, checking into a hotel, applying for a bank loan, etc. Various aspects of the intiative are of general interest for services offered over the internet, including: - Qualification of web sites and services, to ensure they are trustworthy and reliable. This could (partially) address threats such as phishing and illegitimate services; - An electronic signature framework, to express agreement to the content of a document; - A means to demonstrate that a set of data existed at a specific time, e.g., that a bill or fine was paid on time; - A 'seal of authenticity' that can be attached to digital content, such as football tickets, to avoid counterfeit in the digital domain. B.3 Example use cases Use cases include identification on public websites, but also for banking or medical services, education, mobility, etc. It generally involves making life easier for citizens and businesses by producing a framework of trust in the exchange of identity papers without the need for verification by physical meeting. The following indented text is a summary of a discussion of "European Digital Identity" [12]. Figure B.3-1: Example of use, applying for a bank loan [12] Benefits for the citizen: - Easy to identify itself - Management of identity information storage and usage permissions Benefits for businesses: - User-friendliness and compliance with user identification legislation. - Reduction in 'business integration requirements' for services, that currently has to contend with diverse documents and processes. Annex C (informative): Change history Change history Date Meeting TDoc CR Rev Cat Subject/Comment New version 08.2023 SA1 103 S1-232605 TS skeleton 0.0.0 08.2023 SA1 103 S1-232074 S1-232406 S1-232407 S1-232076 S1-232623 S1-232419 S1-232620 S1-232412 S1-232421 S1-232080 S1-232422 Scope References Terminology & Acronyms Overview Localized mobile metaverse services Avatar-based real-time communication Digital asset management Performance requirements Security, authorization, privacy Charging aspects Annex - Metaverse 0.1.0 09.2023 SA#101 SP-231018 MCC clean-up 1.0.0 11.2023 SA1 104 S1-233431 S1-233152 S1-233438 S1-233433 S1-233146 S1-233434 S1-233158 S1-233442 cleanup numbering requirements Mobile metaverse service interconnection addition of KPI requirements Digital asset management Addition of Agreed Consolidated Requirements except for Digital Asset Management revising traffic flow KPIs Informative Annex on The EU Digital Identity Wallet Initiative 1.1.0 12.2023 SA#102 SP-231407 MCC clean-up 2.0.0 12.2023 SA#102 SP-231666 2nd MCC clean-up, this time based on S1-233528r2 when v.2.0.0 was based on S1-233528 2.1.0 12.2023 SA#102 - Approved at SA#102 19.0.0 2024-03 SA#103 SP-240202 0001 2 D Correction to Metaverse requirements 19.1.0
|
025654ae449f21f6a2c0a037ab2affe6
|
22.179
|
1 Scope
|
The present document provides the service requirements for operation of the MCPTT Service. MCPTT makes use of capabilities included in Group Communications System Enablers and Proximity Services, with additional requirements specific to the MCPTT Service. The MCPTT Service can be used for public safety applications and maritime safety applications and also for general commercial applications (e.g., utility companies, railways and maritime usage). The requirements in this specification do not apply to GSM or UMTS.
|
025654ae449f21f6a2c0a037ab2affe6
|
22.179
|
2 References
|
The following documents contain provisions which, through reference in this text, constitute provisions of the present document.
- References are either specific (identified by date of publication, edition number, version number, etc.) or non‑specific.
- For a specific reference, subsequent revisions do not apply.
- For a non-specific reference, the latest version applies. In the case of a reference to a 3GPP document (including a GSM document), a non-specific reference implicitly refers to the latest version of that document in the same Release as the present document.
[1] 3GPP TR 21.905: "Vocabulary for 3GPP Specifications".
[2] TSB-102-B: "Project 25 TIA-102 Document Suite Overview".
[3] TIA-603-D: "Land Mobile FM or PM Communications Equipment Measurement and Performance Standards".
[4] TIA-102.BABA: "Vocoder Description".
[5] 3GPP TS 22.278: "Service requirements for the Evolved Packet System (EPS)".
[6] 3GPP TS 22.468: "Group Communication System Enablers for LTE (GCSE_LTE)".
[7] ITU-T Recommendation P.862: "Perceptual evaluation of speech quality (PESQ): An objective method for end-to-end speech quality assessment of narrow-band telephone networks and speech codecs".
[8] ITU-T Recommendation P.862.1: "Mapping function for transforming P.862 raw result scores to MOS-LQO".
[9] ITU-T Recommendation P.863: "Perceptual objective listening quality assessment".
[10] TIA-102.BABG: "Enhanced Vocoder Methods of Measurement for Performance", March 2010.
[11] 3GPP TS 26.190: "Speech codec speech processing functions; Adaptive Multi-Rate - Wideband (AMR-WB) speech codec; Transcoding functions".
[12] 3GPP TS 26.194: "Speech codec speech processing functions; Adaptive Multi-Rate - Wideband (AMR-WB) speech codec; Voice Activity Detector (VAD)".
[13] 3GPP TS 22.011: "Service accessibility".
[14] 3GPP TS 23.122: "Non-Access-Stratum (NAS) functions related to Mobile Stations (MS) in idle mode".
[15] 3GPP TS 22.280: "Mission Critical Services Common Requirements (MCCoRe)".
[16] ISBN 2-7461-1832-4: “UIC Project EIRENE System Requirements Specification”.
[17] ETSI EN 301 515 V3.0.0 (2018-03): “Global System for Mobile communication (GSM); Requirements for GSM operation on railways”.
|
025654ae449f21f6a2c0a037ab2affe6
|
22.179
|
3 Definitions and abbreviations
| |
025654ae449f21f6a2c0a037ab2affe6
|
22.179
|
3.1 Definitions
|
For the purposes of the present document, the terms and definitions given in TR 21.905 [1] and the following apply. A term defined in the present document takes precedence over the definition of the same term, if any, in TR 21.905 [1]. Definitions provided in 3GPP TS 22.280 [15] also apply to this specification.
Affiliated MCPTT Group Member: An MCPTT Group Member who has indicated an interest in the group and is prepared to receive and/or transmit Group Communications from/to the particular MCPTT Group.
Automatic Commencement Private Call: A Private Call in which the initiation of the Private Call does not require any action on the part of the receiving MCPTT User.
Broadcast Group Call: A group call where the initiating MCPTT User expects no response from the other MCPTT Users, so that when his transmission is complete, so is the call.
Call Commencement Mode: This is a setting that determines the conditions under which a call is started.
Dispatcher: An MCPTT User who participates in MCPTT communications for command and control purposes.
Floor control: An arbitration system in an MCPTT Service that determines who has the authority to transmit (talk) at a point in time during an MCPTT call.
Group-Broadcast Group: A collection of groups defined by the MCPTT Administrator (e.g., representing a particular organizational structure) and intended to be the recipients of Broadcast Group Calls.
Group Regroup: The temporary combining of a multiplicity of groups into a single group.
Hang Time: A configurable maximum length of the inactivity (silence) period between consecutive MCPTT transmissions within the same call.
Imminent Peril Call: An urgent MCPTT Group call that highlights the potential of death or serious injury, but is less critical than an MCPTT Emergency Group Call. For example a call prioritized in the event of immediate threat to any human life such as resulting from an MCPTT User's observation of or engagement in a situation involving imminent peril to the general public (e.g., a forest fire about to encircle campers, tanker truck ready to explode near a school, casualties at the scene of a car bombing).
In-progress Emergency: An emergency condition for a group that has been accepted by the MCPTT Service, but has not yet been cancelled by an authorized user.
In-progress Imminent Peril: An imminent peril condition for a group that has been accepted by the MCPTT Service and has not yet been cancelled by an authorized MCPTT User.
Late call entry: An Affiliated MCPTT Group Member joins in an in progress MCPTT Group Call.
Location: The current physical location (i.e., co-ordinates plus estimated accuracy and timestamp) of the MCPTT UE that can be cross-referenced to a map.
Losing audio: Audio of an overridden talker that is routed to selected authorized MCPTT Users.
Manual Commencement Private Call: A Private Call in which the initiation of the Private Call requires the receiving MCPTT User to perform some action to accept or reject the Private Call setup.
MCPTT Administrator: An individual authorized to control parameters of the MCPTT Service for an organization including, for example, user and group definition, user/group aliases, user priorities, group membership/priorities/hierarchies, security and privacy controls.
MCPTT Emergency Alert: A notification from the MCPTT UE to the MCPTT Service that the MCPTT User has an emergency condition.
MCPTT Emergency Group Call: An urgent MCPTT Group call that highlights the potential of death or serious injury to the initiator.
MCPTT Emergency Private Call: An urgent MCPTT Private Call that highlights the potential of death or serious injury to the initiator.
MCPTT Emergency State: A heightened condition of alarm for an MCPTT User indicating a need for immediate assistance due to a personal life-threatening situation.
MCPTT Group: A defined set of MCPTT Users identified independently of transport or network type.
MCPTT Ad hoc Group: The combining of a multiplicity of MCPTT Users into a group based on pre-defined criteria for the duration of a communication.
MCPTT Group Member: An MCPTT User who has been authorized to participate in Group Communications of a particular MCPTT Group.
MCPTT Request: The action taken by an MCPTT User to request the permission to transmit voice on a call.
MCPTT Service: A Push To Talk communication service supporting applications for Mission Critical Organizations and mission critical applications for other businesses and organizations (e.g., utilities, railways) with fast setup times, high availability, reliability and priority handling.
MCPTT system: The collection of applications, services, and enabling capabilities required to provide Mission Critical Push To Talk for a Mission Critical Organization.
MCPTT UE: A UE that enables an MCPTT User to participate in MCPTT Service.
MCPTT User: A user of an MCPTT Service, who has a device with the capability to participate in MCPTT Services.
MCPTT User Profile: The set of information that allows an MCPTT User to employ the MCPTT Service in a given role and/or from a given MCPTT device.
Mission Critical Push To Talk: A group communication service with fast setup times, ability to handle large groups, strong security and priority handling.
Off-Network MCPTT Service: The collection of functions and capabilities required to provide MCPTT using ProSe Discovery and the ProSe Communication path for MCPTT Users using Public Safety ProSe-enabled UEs as a direct communication between UEs.
Partner MCPTT System: Allied MCPTT system that provides MCPTT Services to an MCPTT User based on the MCPTT User Profile that is defined in the Primary MCPTT System of that MCPTT User.
Pre-emption: The act of terminating on-going calls in order to free up resources for a higher priority call request.
Primary MCPTT System: MCPTT system where the MCPTT User Profile of an MCPTT User is defined.
Private Call: A call between a pair of MCPTT Users using the MCPTT Service with or without MCPTT Floor control.
Project 25 RFSS: A Project 25 Radio Frequency (RF) Subsystem as defined in TSB-102-B [2].
Receiving MCPTT Group Member: An Affiliated MCPTT Group Member who is currently receiving Group Communication from an MCPTT Group.
Selected MCPTT Group: The MCPTT Group that a particular Affiliated MCPTT Group Member uses for transmission.
System Call: A special case of a Broadcast Group Call that is transmitted to all users in a dynamically defined geographic area.
Transmitting MCPTT Group Member: An Affiliated MCPTT Group Member who is currently transmitting a Group Communication to a Selected MCPTT Group.
User-Broadcast Group: A collection of users defined by the MCPTT Administrator (e.g., representing a particular organizational structure) and intended to be the recipients of Broadcast Group Calls.
User ID: The main unique identifier for an MCPTT User.
User Regroup: The temporary combining of a multiplicity of users into a new group.
|
025654ae449f21f6a2c0a037ab2affe6
|
22.179
|
3.2 Abbreviations
|
For the purposes of the present document, the abbreviations given in TR 21.905 [1] and the following apply. An abbreviation defined in the present document takes precedence over the definition of the same abbreviation, if any, in TR 21.905 [1].
FIFO First In First Out
GCSE_LTE Group Communication System Enablers for LTE
KPI Key Performance Indicator
MCPTT Mission Critical Push To Talk
MOS-LQO Mean Opinion Score – Listening Quality Objective
P25 Project 25
PESQ Perceptual Evaluation of Speech Quality
POLQA Perceptual Objective Listening Quality Assessment
ProSe Proximity Services
PTT Push To Talk
RFSS Radio Frequency (RF) Subsystem as defined in the TIA-102 specifications (P25)
TETRA Terrestrial Trunked Radio
TIA Telecommunications Industry Association
UIC Union Internationale des Chemins de Fer
|
025654ae449f21f6a2c0a037ab2affe6
|
22.179
|
4 Mission Critical Push To Talk overview
| |
025654ae449f21f6a2c0a037ab2affe6
|
22.179
|
4.1 General
|
A Push To Talk service provides an arbitrated method by which two or more users may engage in communication. Users may request permission to transmit (e.g., traditionally by means of a press of a button). The Mission Critical Push To Talk (MCPTT) service supports an enhanced PTT service, suitable for mission critical scenarios, based upon 3GPP system services. The requirements for Mission Critical Push To Talk (MCPTT) service defined within can also form the basis for a non-mission critical Push To Talk (PTT) service.
The MCPTT Service is intended to support communication between several users (a group call), where each user has the ability to gain access to the permission to talk in an arbitrated manner. However, the MCPTT Service also supports Private Calls between pairs of users. The MCPTT Service builds on the existing 3GPP transport communication mechanisms provided by the 3GPP architectures to establish, maintain, and terminate the actual communication path(s) among the users.
The MCPTT Service also builds upon service enablers: Group Communications System Enablers and Proximity Services. To the extent feasible, it is expected that the end user's experience to be similar regardless if the MCPTT Service is used under coverage of a 3GPP network or based on ProSe without network coverage. To clarify this intent, the requirements are grouped according to applicability to on-network use, off-network use, or both.
Though the MCPTT Service primarily focuses on the use of the 3GPP system there might be users who access the MCPTT Service through non-3GPP access technology, dispatchers and administrators are examples of this. Dispatchers and administrators are special users who have particular admin and call management privileges which normal users might not have. In MCPTT dispatchers can use an MCPTT UE (i.e., 3GPP) or a non-3GPP access connection to the MCPTT Service based on a "dispatcher and Administrator" interface. Through this interface a user is able to access and manage the services related to on the network and those common to on the network and off the network.
The MCPTT Service allows users to request the permission to talk (transmit voice/audio) and provides a deterministic mechanism to arbitrate between requests that are in contention (i.e., Floor control). When multiple requests occur, the determination of which user's request is accepted and which users' requests are rejected or queued is based upon a number of characteristics (including the respective priorities of the users in contention). MCPTT Service provides a means for a user with higher priority (e.g., MCPTT Emergency condition) to override (interrupt) the current talker. MCPTT Service also supports a mechanism to limit the time a user talks (hold the floor) thus permitting users of the same or lower priority a chance to gain the floor.
The MCPTT Service provides the means for a user to monitor activity on a number of separate calls and enables the user to switch focus to a chosen call. An MCPTT Service user may join an already established MCPTT Group call (Late call entry). In addition the MCPTT Service provides the User ID of the current speaker(s) and user's Location determination features.
The users of an MCPTT Service may have more stringent expectations of performance than the users of a commercial PTT service.
MCPTT is primarily targeting to provide a professional Push To Talk service to e.g., public safety, transport companies, utilities or industrial and nuclear plants. In addition to this a commercial PTT service for non-professional use (e.g., groups of people on holiday) may be delivered through an MCPTT system. Based on their operational model, the performance and MCPTT features in use vary per user organization, where functionality which is more mission critical specific (e.g., Ambient Listening and Imminent Peril Call) might not be available to commercial customers.
MCPTT Users expect to communicate with other MCPTT Users as outlined above, however MCPTT Users also need to be able to communicate with non MCPTT Users using their MCPTT UEs for normal telephony services.
|
025654ae449f21f6a2c0a037ab2affe6
|
22.179
|
4.2 Typical use of the MCPTT Service
|
NOTE: Even though this subclause is written from an organization specific perspective the text is illustrative for typical use of MCPTT Services by all MCPTT Users.
Public safety workers often operate in groups and perform different tasks during the day/week. Many tasks and operations are controlled, assisted and/or coordinated by a dispatcher.
For their communications public safety workers are organized in groups. People that are working together communicate in the same MCPTT Group, the group communication helping them to coordinate quickly.
People with different tasks often communicate in separate MCPTT Groups.
Many of the public safety tasks are routine tasks, that are handled by standard procedures and communication structures, using dedicated MCPTT Groups. Communication structures and MCPTT Groups are also prepared for the handling of large incidents and control of large events. Similarly there are MCPTT Groups and procedures for coordination with public safety workers from other organizations and/or other countries.
The standard procedures and communication structures help the public safety workers to do their work successfully. This results in a long list of (>100) MCPTT Groups available to a public safety worker, from which the correct one is selected depending on the task. To help the public safety worker to quickly find and select the correct MCPTT Group for the task, the MCPTT Groups in the radio are often structured in folders and/or accessible via key-shortcuts. In addition to pre-established MCPTT Groups that users select, there are also provisions in MCPTT systems to merge MCPTT Groups and to select on behalf of a user which group they should be using and for a dispatcher to push them onto it. The large number of MCPTT Groups provisioned on devices is helpful for the device to be able to operate on the network and off the network. However the ability to provision over the air is also seen as a very useful feature, as currently Land Mobile Radio devices often have to be locally re-programmed, rather than updated over the air.
|
025654ae449f21f6a2c0a037ab2affe6
|
22.179
|
4.3 Overview of MCPTT Group affiliation, call and transmission
|
An MCPTT Service provides Group Call and Private Call capabilities, which have various process flows, states and permissions associated with them. The figure 4.3.1, figure 4.3.2, and figure 4.3.3 indicate the high level flows, states and permissions associated with Group Calls and Private Calls. The diagrams apply to the on-network case and off-network case, as from a user perspective the service and concepts should appear similar on the network and off the network. From a technical perspective there might be differences between the on-network states and off-network states (e.g., off the network Affiliation might not require notifying an application server of a user's affiliation and there might also be other differences in the detail depending on the extent to which the off-network capabilities can match the on-network capabilities).
If an MCPTT User wants to communicate with an MCPTT Group they have to be allowed to access the MCPTT Group (i.e., be an MCPTT Group Member), they then have to affiliate and then can have an MCPTT Group as their Selected MCPTT Group. If an MCPTT User is only affiliated to a group this is so that they can receive from the group, however if an MCPTT User has a Selected MCPTT Group this is their group for transmitting on. The differences in states enable an MCPTT User to receive from multiple MCPTT Groups, but specify which MCPTT Group they would like to transmit on.
NOTE: This diagram is for illustrative purposes only and does not supersede the requirements. The diagram is not exhaustive and does not include all the different scenarios.
Figure 4.3.1: MCPTT User state diagram- transmit and receive for a particular MCPTT Group
NOTE: This diagram is for illustrative purposes only and does not supersede the requirements. The diagram is not exhaustive and does not include all the different scenarios.
Figure 4.3.2: MCPTT User state diagram- transmit only for a particular MCPTT Group
NOTE: This diagram is for illustrative purposes only and does not supersede the requirements. The diagram is not exhaustive and does not include all the different scenarios.
Figure 4.3.3: MCPTT User state diagram- receive only for a particular MCPTT Group
It is possible for an MCPTT User to be affiliated with one or more MCPTT Groups. Normally, while in operation, an MCPTT User informs the MCPTT Service about which MCPTT Groups he would like to be affiliated to. These affiliations remain in effect until the MCPTT User removes them, or changes them, or signs out of the service. Some MCPTT Users have permanent affiliations to certain MCPTT Groups and those affiliations are set up implicitly (i.e., automatically) when operating on the network. For those users, the MCPTT Group affiliation starts when the MCPTT Service successfully signs in the user and ends when the MCPTT User's explicit or implicit (e.g., due to inactivity or the turning off of all its devices) request to sign out of the MCPTT Service is acknowledged.
Every time a PTT request is granted a user can start an MCPTT transmission or "talk burst". An MCPTT Group Call consists of one or more MCPTT transmissions. Whether two consecutive transmissions from same or different users are part of the same call, or the second transmission starts a new call, depends on the configurable maximum length of the inactivity period between the consecutive MCPTT transmissions. This inactivity period can be seen as a Hang Time that starts at the end of the preceding transmission. While this timer is running, the resources associated with the call stay assigned to the call (except in case of pre-emption), which could reduce the latency of future floor requests for this group versus groups who are not involved in a call. When a new transmission starts during the inactivity period, the timer is stopped, reset and restarted again at the end of that transmission.
The MCPTT Service recognizes a number of "special" group calls including: Broadcast Group Call, Emergency Group Call and Imminent Peril group call.
A Broadcast Group Call can be seen as a special group call with only one MCPTT transmission.
While the In-progress Emergency state or In-progress Imminent Peril state is active, the inactivity period is conceptually set to infinity; i.e., the resources assigned to calls during these states are never released (except in case of pre-emption). An MCPTT Emergency Group Call or an Imminent Peril group call can be seen as having an unspecified number of transmissions: essentially, all the transmissions to a group during In-progress Emergency state or In-progress Imminent Peril are part of the same MCPTT Group Call.
Conditions on starting ("commencement") and continuing an MCPTT call can be established. Usually at least the call initiator (but also other users) are kept informed via notifications of the starting, stopping, queuing, etc., of a call.
In general, commencement conditions are related to the presence on the call (i.e., participation) of certain members of the group, and/or of a minimum number of members, as well as on the availability of resources (e.g., GBR bearers) of proper ARP. If the commencement conditions are not met, the call does not start (it can be queued or rejected). Normally, commencement conditions are not checked for individual transmission within a call.
Continuation conditions are similar (though not required to be identical) to commencement conditions and get re-evaluated when pre-emption, degradation of priority, motion out of communication range, de-selection of the group or de-affiliation (explicit or implicit) occur. If the continuation conditions are not met, the call stops.
|
025654ae449f21f6a2c0a037ab2affe6
|
22.179
|
4.4 General handling of requests
|
Request handling is by no means specific only to MCPTT Service, but it plays a central role in its functionality.
Requests appear in the MCPTT Service in many forms and under many circumstances: e.g., requests for the floor during a call, requests for starting a call, requests for resources. Conceptually, requests are accompanied by priority information that is used in the arbitration, in case of contention; see also subclause 4.6 for a brief explanation and examples on how priority processing is modelled.
Upon arrival, a request is immediately granted, denied, or queued.
If queued, a request can be dropped due to queue overflow (i.e., too many items queued) or can be cancelled by an authorized user, who is usually the initiator of the request. Either way, the net result is that the request is denied.
When a request denial is communicated, the request may be re-requested either manually by user action or automatically. In the automatic case, while the request remains denied, it may be automatically repeated a configurable number of times where a minimum time interval between re-transmissions may also be applied.
There are many "queuing disciplines" possible that govern the placement of items in a queue and their subsequent removal from the queue: e.g., FIFO, priority order. Assuming that the queuing discipline chosen places the highest priority requests towards the top of the queue, the granted request is either, depending on the design and configuration, the front-most entry in the queue or the first entry counting from the top that can be satisfied by the available resources. For example, if the topmost entry in the queue is awaiting for ten GBR bearers of given characteristics to become available and the second entry in the queue is waiting for seven GBR bearers to become available, and at some point in time eight GBR bearers become available, then it is possible that the second request is granted ahead of the first one, which continues to wait. Alternatively, neither the first request nor the second request is granted and the wait continues until at least ten GBR bearers become available, at which time the first request is granted while the second request continues to wait.
|
025654ae449f21f6a2c0a037ab2affe6
|
22.179
|
4.5 Overview of MCPTT UE and MCPTT User in the MCPTT Service
|
The MCPTT Service supports MCPTT User Profiles. The MCPTT User Profile contains important information related to the MCPTT User receiving the MCPTT Service, including the MCPTT User identity, which is globally unique and independent of the mobile subscriber identity (IMSI) assigned by a 3GPP network operator. Part of the content of the MCPTT User Profile (e.g., containing some display preferences, some UE audio settings, some address books) can be set/modified/updated by the MCPTT User, but significant portions might be set/modified/updated only by authorized persons. The MCPTT User Profile is stored permanently in database(s) associated with the infrastructure providing the MCPTT Service. Relevant parts of the profile might be downloaded to and cached temporarily or permanently on certain MCPTT UEs. When stored on an MCPTT UE, the MCPTT User Profile associated with an MCPTT User might be confidentiality and integrity protected, with the information available only to a trusted application client associated to the MCPTT User, upon authentication. The MCPTT User Profile information can be synchronized automatically or on demand between the cache on the MCPTT UE and the main copy held in the database(s) of the MCPTT Service infrastructure. The MCPTT User Profile is part of the MCPTT application service domain and forms the basis of MCPTT application layer security and identifies an MCPTT User to the MCPTT Service.
Each MCPTT User has at least one MCPTT User Profile, and possibly several. Typically, one of the MCPTT User Profiles is designated as the default MCPTT User Profile, to be used unless an MCPTT User Profile is explicitly selected. In general, a user profile is associated with a specific device, with a specific mode of operation (i.e., on the network or off the network) and/or with a specific situation (e.g., user being off-duty, in a certain city, or playing a certain role). When an MCPTT User Profile is synchronized between the infrastructure and an MCPTT device, information could be downloaded to the device and updated, as necessary. Subsequently and subject to permissions, the MCPTT User might choose a different associated MCPTT User Profile to be downloaded and stored on the device. Only one MCPTT User Profile is active at a time. Authorized users are allowed to create, delete and alter MCPTT User Profiles for an MCPTT User and/or pre-stored MCPTT User Profiles.
The MCPTT Service supports MCPTT UEs which connect to the MCPTT Service. The capabilities of an MCPTT UE are specified in the present document. The MCPTT Application that is resident on the MCPTT UE establishes this connection, employing application layer security in its connection to the MCPTT Service. An MCPTT UE is capable of operating in on-network and off-network modes.
|
025654ae449f21f6a2c0a037ab2affe6
|
22.179
|
4.5.1 MCPTT User association to MCPTT UE in on-network mode
|
Consistent with the 3GPP paradigm, when an MCPTT UE is powered on, it accesses the 3GPP system, and connects to the 3GPP network. During this phase, the credentials from a USIM application (or possibly, an ISIM application, if IMS is used) on a UICC associated with the MCPTT UE is used for authentication with an HSS. This is followed by the MCPTT Application, resident on the MCPTT UE, establishing a connection, employing application layer security in its connection to the MCPTT Service.
Possibilities for the MCPTT UE, when connecting to the MCPTT Service:
- An MCPTT UE, with credentials of an MCPTT User at the time of connection to the MCPTT Service, is able to authenticate using a specific MCPTT User identity (e.g., via an Identity Management service). After successful user authentication the MCPTT User Profiles are made available to the MCPTT UE for use in both on-network and off-network operation modes.
- An MCPTT UE, without credentials of a specific MCPTT User at the time of connection to the MCPTT Service, proceeds using a default identity associated with the MCPTT UE itself. In this case, the MCPTT Service is capable of assigning a temporary MCPTT User Identity to this MCPTT UE. Some level of authentication might be attempted, and, depending on the results, an appropriate MCPTT User Profile associated with this temporary MCPTT User Identity and with the circumstances of the access is made available to the MCPTT UE for use in both on-network and off-network operation modes.
- The MCPTT Administrator is able to retrieve hardware and software parameters to define specific parameters and attributes (e.g., groups, MCPTT Emergency behaviour, priority and QoS attributes) associated with a temporary MCPTT User Identity for operation of the MCPTT UE for use in both on-network and off-network operation modes.
|
025654ae449f21f6a2c0a037ab2affe6
|
22.179
|
4.5.2 MCPTT User and MCPTT UE relationship
|
A user can enter his identifying/authenticating credentials (e.g., user name/ password, PIN, biometrics, asserted identity from a remote, trusted device). This step typically gives the MCPTT User access to local information and applications stored on the MCPTT UE, and in particular, to the MCPTT client application.
The MCPTT Service allows the same MCPTT User to sign in (and stay simultaneously signed in) from different MCPTT UEs. For example, an incident manager or commander might use a portable phone, a command tablet, or a separate messaging unit.
|
025654ae449f21f6a2c0a037ab2affe6
|
22.179
|
4.5.3 MCPTT Users accessing the service through non-3GPP access interface
|
This document primarily focuses on MCPTT Users accessing and managing the MCPTT Service through MCPTT UEs, however there might be some dispatchers and administrators who might access the service through a non-3GPP access interface.
|
025654ae449f21f6a2c0a037ab2affe6
|
22.179
|
4.5.4 Shareable MCPTT UEs and gateway UEs
|
The conceptual model for shareable MCPTT UEs is that of a pool of UEs, each UE being interchangeable with any other, and users randomly choosing one or more UEs from the pool, each user for his temporary exclusive use. A shareable MCPTT UE can be used by user who can gain access to the MCPTT client application stored on it and can become an authenticated MCPTT User. A shareable MCPTT UE can serve only one MCPTT User at a time. An MCPTT User who signs into a shareable MCPTT UE that is already in-use causes the sign-off of the previous MCPTT User.
An MCPTT User can simultaneously have several active MCPTT UEs, which, from an MCPTT Service point of view, are addressable individually and/or collectively within the context of their association to the MCPTT User.
The conceptual model for a gateway UE is that of a UE capable of providing service to an MCPTT User employing a non-3GPP device. A gateway UE is usable simultaneously by multiple MCPTT Users. Unlike a shareable MCPTT UE, if a new person enters his valid credentials towards signing in the MCPTT Service, his successful signing in and becoming an MCPTT User does not affect the initial MCPTT Users already served by the gateway UE.
A gateway UE is typically installed in a vehicle (e.g., a police car, fire truck) and has wired and/or wireless connections to various devices in use by the MCPTT Users.
A gateway UE differs functionally from a ProSe relay node. In the ProSe paradigm, the relay node and the devices served by it are all (ProSe enabled) 3GPP UEs, and are "visible" to the 3GPP system as UEs. In the gateway UE paradigm, only the gateway UE is an 3GPP device and only it is "visible" at the 3GPP network layer.
Figure 4.5.4.1 shows schematically some of the relationships between MCPTT Users and MCPTT UEs.
Figure 4.5.4-1: Relationships between MCPTT Users and MCPTT UEs
|
025654ae449f21f6a2c0a037ab2affe6
|
22.179
|
4.5.5 MCPTT User association to MCPTT UE in off-network mode
|
A user can enter his identifying/authenticating credentials (e.g., user name/ password, PIN, biometrics, asserted identity from a remote, trusted device). This step typically gives the MCPTT User access to local information and applications stored on the MCPTT UE, and in particular, to the MCPTT client application.
After successful local user authentication an MCPTT User Profile, which was previously made available to the MCPTT UE, is used for off-network operation mode. This previously configured MCPTT User Profile information allows the MCPTT User to be identified using the same MCPTT User Identity as in the on-network mode.
An MCPTT UE, without credentials of a specific MCPTT User, operates in off-network mode, if so configured by an MCPTT Administrator. The MCPTT Administrator defines specific parameters and attributes (e.g., groups, MCPTT Emergency behaviour, priority and QoS attributes) associated with a temporary MCPTT User Identity for operation of the MCPTT UE in off-network operation mode.
|
025654ae449f21f6a2c0a037ab2affe6
|
22.179
|
4.6 Overview of MCPTT priorities
| |
025654ae449f21f6a2c0a037ab2affe6
|
22.179
|
4.6.1 MCPTT priority model
|
Many non-public safety 3GPP users today subscribe to one particular priority and QoS level of service (e.g., "gold", "silver" or "bronze"), which always provides fixed differentiation. This model, effective and relatively straightforward for non-public safety users, falls short when it comes to the needs of the public safety applications.
MCPTT Priority and QoS is situational. The MCPTT Service is intended to provide a real-time priority and QoS experience for MCPTT calls, as public safety users have significant dynamic operational conditions that determine their priority. For example, the type of incident a responder is serving or the responder's overall shift role needs to strongly influence a user's ability to obtain resources from the 3GPP system.
Another feature of a mission critical service is transparency of interactions between the users and the system. A first responder that needs to change the QoS of his communications is not to be distracted from his mission due to complicated UE behaviours or service interactions. Instead, the service acts in an anticipatory and adaptive manner to provide the proper quality of experience to the user, automatically, or with simple and minimal interaction.
The mission critical service is also expected to provide the ability to interface with public safety systems (e.g., Computer Aided Dispatch) in order to determine the user's state (e.g., incident severity), environment and conditions and to affect the most appropriate priority and QoS experience for the user.
The MCPTT Priority handling for on-network use for MCPTT Calls is conceptually modelled as shown in figure 4.6.1.1. The conceptual model identifies three areas of prioritization: prioritization between and within calls, inter-system prioritization, and prioritization at the transport layer (3GPP system and UE). At the Application Layer a generic, network side, functional entity, "MCPTT Priority and QoS Control", processes with each request static, preconfigured information about users and groups participating in MCPTT, as well as dynamic (or situational) information about them. Based on the results of this processing, the "MCPTT Priority and QoS Control" provides information to and directs interactions with other functional entities, systems, or layers to ensure, to the extent possible, that from a quality of experience point of view, calls and transmissions are handled properly in accordance to established policy rules.
Error! Objects cannot be created from editing field codes.
Figure 4.6.1-1: A conceptual on-network MCPTT priority model
The User Static Attributes include information categorizing the user, possibly by several criteria (e.g., first responder, second responder, supervisor, dispatcher, administrator), as well as jurisdictional boundaries and possibly a preconfigured system-wide individual priority level.
The Group Static Attributes include information about the nature/type of the group and the owning organization(s), the jurisdictional boundaries for transmitters and receivers within the group, the normal hours of operation for the group, pre-emption dispositions relative to other groups, and the default minimum priority of the group, i.e., the minimum priority characteristics that are provided to all the Participants in a group call associated with this group, regardless of their individual priority characteristics.
The User Dynamic Attributes include the user/Participant's operational status (e.g., on/off duty), his location, the type of incident (e.g., MCPTT Emergency or Imminent Peril) he might be involved in and whether or not he initiated it, whether or not he is individually involved in a formally managed incident and if yes, the boundaries of the incident area, the incident severity and his assigned role in the resolution of the incident.
The Group Dynamic Attributes include the type of incident (e.g., MCPTT Emergency or Imminent Peril), if any, the group is currently handling and in case of involvement in a formally managed incident the boundaries of the incident area and the incident severity.
|
025654ae449f21f6a2c0a037ab2affe6
|
22.179
|
4.6.2 Generic processing of priority information
|
This functionality applies to MCPTT Call initiations and transmissions for the management of potentially contended resources (e.g., GBR bearers) and also for Floor control during an MCPTT Group Call.
Each request for exclusive access to resource(s) or for preferential treatment over a contending request arrives accompanied by priority information. This information stays associated with the companion request, whether the request is granted or is queued. The priority information is used for comparison between requests and facilitates the adding and removing of requests from queues and/or authorized interruption of service associated with a previously granted request, if still active. For each request, whether initially queued or not, the requesting party is informed (directly or indirectly) when his request is granted or denied. Other users/Participants are also notified of the disposition of a request and the notification includes the identity of the requestor, as needed. In addition, each requestor can be notified of the position of his request in the queue and he is allowed to cancel his requests while queued.
|
025654ae449f21f6a2c0a037ab2affe6
|
22.179
|
4.6.3 Handling of MCPTT priority information for Floor control
|
Floor control is applied in the context of a single MCPTT Call and is triggered by a Participant request for the permission to transmit. Priority information accompanies each grant request.
|
025654ae449f21f6a2c0a037ab2affe6
|
22.179
|
4.6.4 Handling of MCPTT priority information for interactions at the transport layer
|
At the Transport Layer, the MCPTT Service uses3GPP controls to adapt the overall behaviour of the MCPTT System to the needs for resources and/or preferential treatment over other contenders, based on the priority information accompanying the request.
The following four controls are available, to be used as necessary, based on the phase of the MCPTT call:
• 3GPP system Access Controls;
• UE Access Controls;
• 3GPP system Admission Controls; and
• 3GPP system Scheduling Controls.
3GPP system Access Controls and UE Access Controls are used to allow preferential treatment of public safety UEs in situations of access congestion. The controls use priority and QoS mechanisms (e.g., using mechanisms like Access Class Barring, Service Specific Access Control, Access Control for Circuit Switched Fallback, Extended Access Barring).
Admission Controls are used for the establishment and maintenance of the priority levels and of the pre-emption vulnerability and capability of bearers associated with transmissions and calls. At the start of an MCPTT call, the MCPTT Service requires bearers with proper ARP and pre-emption characteristics are in place prior to the call proceeding.
Scheduling Controls (e.g., QCI and bandwidth for the bearers) are used for assuring the appropriate QoS necessary for meeting the Participants' expectation in the perceived quality of the delivered information, primarily in terms of when the service starts and the real-time characteristics of the delivered traffic (e.g., perceived delay, choppiness, clarity).
|
025654ae449f21f6a2c0a037ab2affe6
|
22.179
|
4.6.5 Handling of MCPTT priority information for interactions with non-3GPP PTT systems
|
An MCPTT call can be mixed, with some Participants served by one network/system and other Participants served by a different network(s)/system(s). In general the systems can be quite different. For example, some Participants use MCPTT/LTE, while others could use a P25-based system.
|
025654ae449f21f6a2c0a037ab2affe6
|
22.179
|
4.6.6 MCPTT priority for Private Call
|
The MCPTT Service uses User Static Attributes of the Participants, potentially adjusted based on User Dynamic Attributes, if applicable. By default, the priority of an MCPTT Private Call is the same as the priority of the originator of the call. Similar to group calls there are MCPTT Emergency Private Calls (with Floor control), which also have a similarly high priority. These are used where there is immediate danger to the user and are typically used to communicate with a dispatcher.
|
025654ae449f21f6a2c0a037ab2affe6
|
22.179
|
4.7 Overview of MCPTT identifiers
|
The main identifiable entities in use by the MCPTT Service are Mission Critical Organizations, MCPTT Groups, MCPTT Users, and MCPTT Administrators. The UEs are identified at the transport or network layer, but in some situations they might also be identified by the MCPTT Service. Each identifiable entity is distinct from all others and has an identifier (ID) associated to it, unique within a proximate identity domain. Those domains correspond to identifiable entities and can be nested within other domains in a multi-level hierarchical fashion. For example an MCPTT User might have an identifier unique within the domain corresponding to a Mission Critical Organization. The top-down concatenation of identifiers can generate unique identifiers within larger contexts, eventually leading to the identifiers being globally unique.
Each identifier can be associated with one or more aliases, which can be used for displaying and selection purposes. Some aliases are shortened equivalents of the identifier used for efficient signalling and are not intended for human interactions. At a minimum, each entity has one alias (default) which is the alphanumeric representation of its identifier. Most entities have a main alias, which is the entity's name. Some aliases can be pictures, icons or other graphic representations. It is up to the implementation to decide if aliases have to be unique and if so, within which domain. Finally, some aliases are public, can be created/deleted only by authorized persons and are available to the MCPTT Service, while other aliases are private, can be created/deleted by their owners and might be residing only on certain UEs or be part of some private address books.
It is possible in principle for User IDs, Group IDs, as well as for aliases, to be defined system wide with certain values, but have different values for each application: e.g., the system wide User ID might be different from the MCPTT User ID and different from the video User ID for the same user. However, this type of separation might not be beneficial, and in practice only one identifier is likely to be used.
For simplicity, the term "User ID" is employed to identify an MCPTT User, without distinction of whether it is an identifier or an alias.
|
025654ae449f21f6a2c0a037ab2affe6
|
22.179
|
5 MCPTT Service requirements common for on the network and off the network
| |
025654ae449f21f6a2c0a037ab2affe6
|
22.179
|
5.1 General group call requirements
| |
025654ae449f21f6a2c0a037ab2affe6
|
22.179
|
5.1.1 General aspects
|
[R-5.1.1-001] Void
[R-5.1.1-002] Void
[R-5.1.1-003] Void
[R-5.1.1-004] Void
[R-5.1.1-005] Void
|
025654ae449f21f6a2c0a037ab2affe6
|
22.179
|
5.1.2 Group/status information
|
[R-5.1.2-001] Void
[R-5.1.2-002] Void
|
025654ae449f21f6a2c0a037ab2affe6
|
22.179
|
5.1.3 Group configuration
|
[R-5.1.3-001] Void
[R-5.1.3-002] Void
|
025654ae449f21f6a2c0a037ab2affe6
|
22.179
|
5.1.4 Identification
|
[R-5.1.4-001] Void
|
025654ae449f21f6a2c0a037ab2affe6
|
22.179
|
5.1.5 Membership/affiliation
|
[R-5.1.5-001] Void
[R-5.1.5-002] Void
[R-5.1.5-003] Void
[R-5.1.5-004] Void
[R-5.1.5-005] Void
[R-5.1.5-006] Void
[R-5.1.5-007] Void
[R-5.1.5-008] Void
|
025654ae449f21f6a2c0a037ab2affe6
|
22.179
|
5.1.6 Group Call administration
|
[R-5.1.6-001] Void
|
025654ae449f21f6a2c0a037ab2affe6
|
22.179
|
5.1.7 Prioritization
|
[R-5.1.7-001] Void
[R-5.1.7-002] Void
|
025654ae449f21f6a2c0a037ab2affe6
|
22.179
|
5.1.8 Charging requirements for MCPTT
|
[R-5.1.8-001] Void
[R-5.1.8-002] Void
[R-5.1.8-003] Void
[R-5.1.8-004] Void
[R-5.1.8-005] Void
[R-5.1.8-006] Void
[R-5.1.8-007] Void
[R-5.1.8-008] Void
[R-5.1.8-009] Void
[R-5.1.8-010] Void
[R-5.1.8-011] Void
|
025654ae449f21f6a2c0a037ab2affe6
|
22.179
|
5.2 Broadcast Group
| |
025654ae449f21f6a2c0a037ab2affe6
|
22.179
|
5.2.1 General Broadcast Group Call
|
[R-5.2.1-001] Void
[R-5.2.1-002] Void
|
025654ae449f21f6a2c0a037ab2affe6
|
22.179
|
5.2.2 Group-Broadcast Group (e.g., announcement group)
|
[R-5.2.2-001] Void
[R-5.2.2-002] Void
[R-5.2.2-003] Void
[R-5.2.2-004] Void
|
025654ae449f21f6a2c0a037ab2affe6
|
22.179
|
5.2.3 User-Broadcast Group (e.g., System Call)
|
[R-5.2.3-001] Void
[R-5.2.3-002] Void
|
025654ae449f21f6a2c0a037ab2affe6
|
22.179
|
5.3 Late call entry
|
[R-5.3-001] Void
[R-5.3-002] Void
[R-5.3-003] Void
[R-5.3-004] Void
[R-5.3-005] Void
|
025654ae449f21f6a2c0a037ab2affe6
|
22.179
|
5.4 Dynamic group management (i.e., dynamic regrouping)
|
NOTE: No common on-network and off-network dynamic group management requirements have been identified.
|
025654ae449f21f6a2c0a037ab2affe6
|
22.179
|
5.5 Receiving from multiple MCPTT calls
| |
025654ae449f21f6a2c0a037ab2affe6
|
22.179
|
5.5.1 Overview
|
MCPTT Users receive call traffic of their affiliated MCPTT Groups. This multiple receiving, called monitoring by some organizations, provides MCPTT Users current information about police, fire or critical medical events that are occurring within their jurisdictions. This is useful for dispatchers or those that might not be the primary support for that event at that moment. The information gained by monitoring might be useful for the dispatcher to determine any actions to take or be useful later if the MCPTT User is deployed to provide additional support for that event. The MCPTT User might be assigned to support the activities of more than one MCPTT Group on the same shift. This means that the MCPTT User receives multiple MCPTT Groups.
An MCPTT User with limited speaker resources (e.g., a handheld UE) might find that playing out concurrent received audio from multiple active MCPTT Groups becomes confusing and could also cause undesired voice distortion for the receiving user. During periods of time when the MCPTT User is receiving audio from multiple MCPTT Groups, which MCPTT Group's audio is presented to the MCPTT User is determined by the MCPTT User's choice, the priority associated with the talker of the Selected MCPTT Group(s), other considerations or combinations of these. The MCPTT UE is aware of all the active groups to which the MCPTT User has affiliated or selected and the identity of the other active receiving groups is available for display on the MCPTT UE. When the receive activity from the Selected MCPTT Group stops, the MCPTT UE might present the audio from the next group per the MCPTT User's choice or by other means.
If none of the multiple groups to which the MCPTT User has affiliated or selected is active, the MCPTT UE would continue to monitor for activity by any of the multiple affiliated or Selected MCPTT Groups. Monitoring for activity of multiple MCPTT Groups is also known as scanning and the list of the multiple groups is also known as a scan list.
|
025654ae449f21f6a2c0a037ab2affe6
|
22.179
|
5.5.2 Requirements
|
[R-5.5.2-001] Void
[R-5.5.2-002] Void
[R-5.5.2-003] Void
[R-5.5.2-004] Void
[R-5.5.2-005] Void
[R-5.5.2-006] The MCPTT Service shall provide a mechanism for an MCPTT Administrator to limit the total number (N5) of MCPTT Group transmissions that an MCPTT UE simultaneously receives in one MCPTT Group call in case of override.
[R-5.5.2-007] The MCPTT Service shall provide a mechanism for an MCPTT Administrator to limit the total number (N10) of MCPTT Private Calls (with Floor control) in which an MCPTT UE simultaneously participates.
[R-5.5.2-008] Void
[R-5.5.2-009] The MCPTT Service shall provide a mechanism for an MCPTT Administrator to limit the total number (N7) of MCPTT Group transmissions that an MCPTT User simultaneously receives in one MCPTT Group call in case of override.
[R-5.5.2-010] Void
[R-5.5.2-011] Void
[R-5.5.2-012] Void
[R-5.5.2-013] Void
|
025654ae449f21f6a2c0a037ab2affe6
|
22.179
|
5.6 Private Call
| |
025654ae449f21f6a2c0a037ab2affe6
|
22.179
|
5.6.1 Private Call overview
|
Private Calls allow two MCPTT Users to communicate directly with each other without the use of MCPTT Groups. They leverage many of the functions and features of MCPTT Group Calls, such as MCPTT User identity and alias information, location information, encryption, privacy, priority, and administrative control. Private Calls can use Floor control or not (i.e., be full voice duplex calls between users), though Private Calls without Floor control are only supported on the network.
Two commencement modes of Private Calls are supported: Manual Commencement Private Call and Automatic Commencement Private Call. The two commencement modes can be used in conjunction with Private Calls with/without Floor control.
Manual Commencement Private Calls mimic a telephone conversation where the called party receives a notification that they are being requested to join a Private Call, and the called party may accept, reject, or ignore the call request. Once the call setup is accepted, the Private Call is established and both Participants may communicate with each other.
Automatic Commencement Private Calls mimic the immediate setup and voice propagation of Group Call operation between two users where the calling party initiates an Automatic Commencement Private Call to another user and sends audio without any additional call setup delay beyond Group Calls. If available and able to accept the Private Call from the calling party, the called party immediately joins the Private Call and processes the calling party's audio.
|
025654ae449f21f6a2c0a037ab2affe6
|
22.179
|
5.6.2 Private Call (with Floor control) general requirements
|
NOTE: The requirements in this subclause should mirror requirements in 6.7.1 for Private Call (without Floor control).
[R-5.6.2-001] The MCPTT Service shall provide the status (e.g., ringing, accepted, rejected, active) of an MCPTT Private Call (with Floor control) to the relevant MCPTT User that is a Participant of the MCPTT Private Call (with Floor control).
[R-5.6.2-002] The MCPTT Service shall support Private Calls with Floor control.
[R-5.6.2-003] The MCPTT Service shall provide a mechanism for an authorized MCPTT User that is a called party in an MCPTT Private Call (with Floor control), to restrict providing the reason why an MCPTT Private Call (with Floor control) setup has failed to the calling MCPTT User.
[R-5.6.2-004] The MCPTT Service shall provide a mechanism for the Private Call (with Floor control) to be set up with the MCPTT UE designated by the called MCPTT User to be used for Private Calls (with Floor control) when the called MCPTT User has signed on to the MCPTT Service with multiple MCPTT UEs.
[R-5.6.2-005] Void
|
025654ae449f21f6a2c0a037ab2affe6
|
22.179
|
5.6.3 Private Call (with Floor control) commencement requirements
|
NOTE 1: The requirements in this subclause should mirror the requirements in 6.7.4 for Private Call (without Floor control).
[R-5.6.3-001] The MCPTT Service shall support Call Commencement Modes for Private Calls (with Floor control), which determine the conditions under which Private Calls (with Floor control) are set up.
[R-5.6.3-002] Void
[R-5.6.3-003] The MCPTT Service shall provide a mechanism for an MCPTT User to cancel an MCPTT Private Call (with Floor control) prior to the call setup.
[R-5.6.3-004] The MCPTT Service shall provide a means by which an authorized MCPTT User initiates an MCPTT Private Call (with Floor control).
[R-5.6.3-005] The MCPTT Service shall provide a means by which an MCPTT UE initiates an MCPTT Private Call (with Floor control) to any MCPTT User for which the MCPTT UE's current MCPTT User is authorized.
NOTE 2: For off-network use, only an MCPTT UE within communication range (possibly via a ProSe UE-to-UE Relay) receives the transmission.
[R-5.6.3-006] The MCPTT Service shall provide a means by which an MCPTT User initiates a Manual Commencement Private Call (with Floor control) to any MCPTT User for which the MCPTT User is authorized.
[R-5.6.3-007] The MCPTT Service shall require that the called MCPTT User accepts a Manual Commencement Private Call (with Floor control) setup request before the call proceeds.
[R-5.6.3-008] The MCPTT Service shall provide a means for an MCPTT User to accept a Manual Commencement Private Call (with Floor control) request from another MCPTT User.
[R-5.6.3-009] The MCPTT Service shall provide a means by which an MCPTT User initiates an Automatic Commencement Private Call (with Floor control) to any MCPTT User for which the MCPTT User is authorized.
[R-5.6.3-010] The MCPTT UE shall support automatic commencement mode and manual commencement mode for Private Calls (with Floor control).
[R-5.6.3-011] The MCPTT Service shall provide a manual commencement mode countermand by which an authorized MCPTT User may request that the invited MCPTT UE answer automatically.
[R-5.6.3-012] The MCPTT Service shall provide a means by which the calling authorized MCPTT User is notified the called MCPTT User received the Private Call (with Floor control) request.
[R-5.6.3-013] The MCPTT Service shall require that the called MCPTT UE acknowledge receipt of an Automatic Commencement Private Call (with Floor control) setup request before the audio transmission proceeds.
[R-5.6.3-014] The MCPTT Service shall provide a mechanism for an authorized MCPTT User to transfer an ongoing MCPTT Private Call (with Floor control) to another MCPTT user.
[R-5.6.3-015] The MCPTT Service shall provide a mechanism for an authorized MCPTT User to configure forwarding of incoming MCPTT Private Calls (with Floor control) to another MCPTT user in the following situations:
- Always
- If the MCPTT User is not reachable
- If the incoming private call is a call with manual commencement mode and the MCPTT User does not answer within a configured period
- Based on manual input of the MCPTT User
|
025654ae449f21f6a2c0a037ab2affe6
|
22.179
|
5.6.4 Private Call (with Floor control) termination
|
NOTE 1: The requirements in this subclause should mirror the requirements in 6.7.5 for Private Call (without Floor control).
[R-5.6.4-001] The MCPTT Service shall provide a mechanism for an MCPTT User to reject an MCPTT Private Call (with Floor control).
[R-5.6.4-002] The MCPTT Service shall provide a means by which an authorized MCPTT User ignores a Manual Commencement Private Call (with Floor control) request from another MCPTT User.
NOTE 2: Ignoring a Manual Commencement Private Call (with Floor control) results in no indication of the reason for call failure being sent to the calling MCPTT User.
[R-5.6.4-003] The MCPTT Service shall provide a means by which an MCPTT User ends a Private Call (with Floor control) in which the MCPTT User is a Participant.
|
025654ae449f21f6a2c0a037ab2affe6
|
22.179
|
5.6.5 Private Call (with Floor control) administration
|
NOTE: The requirements in this subclause should mirror requirements in 6.7.2 for Private Call (without Floor control), except [R-5.6.5-005] which is specific to Private Call with Floor control.
[R-5.6.5-001] The MCPTT Service shall provide a mechanism for an MCPTT Administrator to configure which MCPTT Users, within their authority, are authorized to place a Manual Commencement Private Call (with Floor control).
[R-5.6.5-002] The MCPTT Service shall provide a mechanism for an MCPTT Administrator to configure which MCPTT Users, within their authority, are authorized to place an Automatic Commencement Private Call (with Floor control).
[R-5.6.5-003] The MCPTT Service shall provide a mechanism for an MCPTT Administrator to configure for a particular authorized MCPTT User, a set of MCPTT Users under the same authority to which an MCPTT Private Call (with Floor control) can be made.
[R-5.6.5004] The MCPTT Service shall provide a mechanism for an MCPTT Administrator to configure the maximum duration for MCPTT Private Calls (with Floor control) for MCPTT Users within their authority.
[R-5.6.5-005] The MCPTT Service shall provide a mechanism for an MCPTT Administrator to configure a timeout value in which an MCPTT Private Call (with Floor control) without a transmitting or receiving MCPTT User ends, for MCPTT Users within their authority.
[R-5.6.5-006] The MCPTT Service shall provide a mechanism for an MCPTT Administrator to configure whether an MCPTT User, within their authority, that is a called party in an MCPTT Private Call (with Floor control), may restrict providing the reason why an MCPTT Private Call (with Floor control) setup has failed to the calling MCPTT User.
|
025654ae449f21f6a2c0a037ab2affe6
|
22.179
|
5.7 MCPTT priority requirements
| |
025654ae449f21f6a2c0a037ab2affe6
|
22.179
|
5.7.1 Overview
|
MCPTT Emergency Group Call and MCPTT Imminent Peril group call are MCPTT Group Calls that provide the MCPTT User elevated priority towards obtaining resources of the MCPTT system. The MCPTT Emergency Private Call similarly provides elevated priority to resources of the MCPTT system. The MCPTT Emergency Alert provides a notification of an MCPTT Emergency situation from an MCPTT UE, regardless if the user is signed in with the MCPTT Service or not.
The MCPTT Emergency Alert is initiated from an MCPTT UE to inform the MCPTT Service of the user's immediate need of assistance due to the user's personal, life-threatening situation. If the user is not properly authenticated, he is treated as a temporary MCPTT User with limited permissions. The user initiates this notification by actuating a user interface on the MCPTT UE. The notification to the MCPTT Service includes the MCPTT User's ID, potentially an MCPTT Group ID, the user's Mission Critical Organization name and the most current location available for the user's MCPTT UE.
The user profile/group configuration determines which MCPTT Group ID is used, if any. If the user profile indicates that a dedicated (i.e., not used for everyday traffic) MCPTT Emergency Group is to be used, then the MCPTT Emergency call traffic moves to a different group. MCPTT Users that support MCPTT Emergency situations are required to monitor the dedicated MCPTT Emergency Group(s) for call activity. If the user profile indicates that the selected (i.e., currently active) MCPTT Group is to be used, then its Group ID is used, unless no group is selected.
After the MCPTT User has initiated an MCPTT Emergency Alert, MCPTT Emergency Private Call or MCPTT Emergency Group Call, the MCPTT User is considered to be in the MCPTT Emergency State. The user remains in the MCPTT Emergency State until the MCPTT User cancels the MCPTT Emergency State.
An MCPTT Group Call started by an MCPTT User while in the MCPTT Emergency State or previously started but followed by an MCPTT Emergency Alert becomes an MCPTT Emergency Group Call. The MCPTT Group ID used for the MCPTT Emergency Group Call is the same MCPTT Group ID included in the MCPTT Emergency Alert. An MCPTT User or dispatcher might initiate an MCPTT Emergency Group Call without an MCPTT Emergency Alert. The start of an MCPTT Emergency Group Call starts an In-progress Emergency condition for the MCPTT Group. Any subsequent MCPTT Group Call made by any MCPTT Group Member of an MCPTT Group which has an In-progress Emergency is treated as an MCPTT Emergency Group Call. MCPTT Emergency Group priority is removed when the In-progress Emergency for the group is cancelled.
An MCPTT Private Call started by an MCPTT User while in the MCPTT Emergency State becomes an MCPTT Emergency Private Call.
MCPTT Imminent Peril group call is differentiated from MCPTT Emergency Group Call based on for whom the assistance is required. The MCPTT Emergency Group Call is initiated by an MCPTT User for assistance for the MCPTT Emergency condition involving that user. The MCPTT Imminent Peril group call is initiated by an MCPTT User for assistance to other MCPTT Users or persons of the general public observed to be in trouble and may soon need assistance.
There is no MCPTT Imminent Peril Alert and no MCPTT Imminent Peril State for MCPTT Users. The granting of an MCPTT Imminent Peril group call starts an In-progress Imminent Peril condition for the MCPTT Group. Any subsequent MCPTT Group Call made by any MCPTT Group Member of an MCPTT Group which has an In-progress Imminent Peril condition is treated as an MCPTT Imminent Peril group call. MCPTT Imminent Peril Group priority is removed when the In-progress Imminent Peril for the group is cancelled.
|
025654ae449f21f6a2c0a037ab2affe6
|
22.179
|
5.7.2 Call types based on priorities
| |
025654ae449f21f6a2c0a037ab2affe6
|
22.179
|
5.7.2.1 MCPTT Emergency Group Call
| |
025654ae449f21f6a2c0a037ab2affe6
|
22.179
|
5.7.2.1.1 MCPTT Emergency Group Call requirements
|
[R-5.7.2.1.1-001] Void
[R-5.7.2.1.1-002] Void
[R-5.7.2.1.1-003] Void
[R-5.7.2.1.1-004] Void
[R-5.7.2.1.1-005] Void
[R-5.7.2.1.1-006] Void
[R-5.7.2.1.1-007] Void
[R-5.7.2.1.1-008] Void
[R-5.7.2.1.1-009] Void
[R-5.7.2.1.1-010] Void
[R-5.7.2.1.1-011] Void
[R-5.7.2.1.1-012] Void
[R-5.7.2.1.1-013] Void
[R-5.7.2.1.1-014] Void
|
025654ae449f21f6a2c0a037ab2affe6
|
22.179
|
5.7.2.1.2 MCPTT Emergency Group Call cancellation requirements
|
[R-5.7.2.1.2-001] Void
[R-5.7.2.1.2-002] Void
[R-5.7.2.1.2-003] Void
[R-5.7.2.1.2-004] Void
[R-5.7.2.1.2-005] Void
|
025654ae449f21f6a2c0a037ab2affe6
|
22.179
|
5.7.2.2 Imminent Peril group call
| |
025654ae449f21f6a2c0a037ab2affe6
|
22.179
|
5.7.2.2.1 Imminent Peril group call requirements
|
[R-5.7.2.2.1-001] Void
[R-5.7.2.2.1-002] Void
[R-5.7.2.2.1-003] Void
[R-5.7.2.2.1-004] Void
[R-5.7.2.2.1-005] Void
[R-5.7.2.2.1-006] Void
[R-5.7.2.2.1-007] Void
[R-5.7.2.2.1-008] Void
[R-5.7.2.2.1-009] Void
|
025654ae449f21f6a2c0a037ab2affe6
|
22.179
|
5.7.2.2.2 Imminent Peril group call cancellation requirements
|
[R-5.7.2.2.2-001] Void
[R-5.7.2.2.2-002] Void
[R-5.7.2.2.2-003] Void
[R-5.7.2.2.2-004] Void
|
025654ae449f21f6a2c0a037ab2affe6
|
22.179
|
5.7.2.3 MCPTT Emergency Private Call (with Floor control)
| |
025654ae449f21f6a2c0a037ab2affe6
|
22.179
|
5.7.2.3.1 MCPTT Emergency Private Call (with Floor control) requirements
|
[R-5.7.2.3.1-001] The MCPTT Service shall support MCPTT Emergency Private Calls (with Floor control) from authorized MCPTT Users.
NOTE: This functionality out of network relies on the MCPTT User being called being within ProSe Communication range. For this reason this functionality is more likely to be used on the network.
[R-5.7.2.3.1-002] When an MCPTT User initiates an MCPTT Emergency Private Call (with Floor control) this may trigger an MCPTT Emergency Alert for that MCPTT User.
[R-5.7.2.3.1-003] When an MCPTT User initiates an MCPTT Emergency Private Call (with Floor control) this shall put that MCPTT User into an MCPTT Emergency State.
|
025654ae449f21f6a2c0a037ab2affe6
|
22.179
|
5.7.2.3.2 MCPTT Emergency Private Call (with Floor control) cancellation requirements
|
[R-5.7.2.3.2-001] The MCPTT Service shall support cancellation of the MCPTT Emergency priority of an MCPTT Emergency Private Call (with Floor control) by an authorized MCPTT User.
[R-5.7.2.3.2-002] The MCPTT Service shall support cancellation of the MCPTT Emergency priority of an MCPTT Emergency Private Call (with Floor control) when criteria established by the MCPTT Administrator are met (e.g., timeout).
[R-5.7.2.3.2-003] The MCPTT Service shall support an MCPTT User cancelling their own MCPTT Emergency State.
|
025654ae449f21f6a2c0a037ab2affe6
|
22.179
|
5.7.2.4 MCPTT Emergency Alert
| |
025654ae449f21f6a2c0a037ab2affe6
|
22.179
|
5.7.2.4.1 MCPTT Emergency Alert requirements
|
[R-5.7.2.4.1-001] Void
[R-5.7.2.4.1-002] Void
[R-5.7.2.4.1-003] Void
[R-5.7.2.4.1-004] Void
[R-5.7.2.4.1-005] Void
[R-5.7.2.4.1-006] Void
[R-5.7.2.4.1-007] Void
[R-5.7.2.4.1-008] Void
[R-5.7.2.4.1-009] Void
[R-5.7.2.4.1-010] Void
[R-5.7.2.4.1-011] Void
[R-5.7.2.4.1-012] Void
|
025654ae449f21f6a2c0a037ab2affe6
|
22.179
|
5.7.2.4.2 MCPTT Emergency Alert cancellation requirements
|
[R-5.7.2.4.2-001] Void
[R-5.7.2.4.2-002] Void
[R-5.7.2.4.2-003] Void
|
025654ae449f21f6a2c0a037ab2affe6
|
22.179
|
5.8 User ID
|
[R-5.8-001] Void
[R-5.8-002] Void
[R-5.8-003] Void
|
025654ae449f21f6a2c0a037ab2affe6
|
22.179
|
5.9 MCPTT UE management
|
[R-5.9-001] Void
[R-5.9-002] Void
|
025654ae449f21f6a2c0a037ab2affe6
|
22.179
|
5.10 MCPTT User Profile
|
[R-5.10-001] Void
[R-5.10-002] Void
|
025654ae449f21f6a2c0a037ab2affe6
|
22.179
|
5.11 Support for multiple devices
|
[R-5.11-001] Void
[R-5.11-002] Void
|
025654ae449f21f6a2c0a037ab2affe6
|
22.179
|
5.12 Location
|
[R-5.12-001] Void
[R-5.12-002] Void
[R-5.12-003] Void
[R-5.12-004] Void
[R-5.12-005] Void
[R-5.12-006] Void
[R-5.12-007] Void
[R-5.12-008] Void
[R-5.12-009] Void
[R-5.12-010] Void
[R-5.12-011] The MCPTT Service shall provide a means for an MCPTT UE to send a Location information update whenever the MCPTT User initiates an MCPTT Imminent Peril Call.
[R-5.12-012] Void
[R-5.12-013] Void
[R-5.12-014] Void
[R-5.12-015] Void
|
025654ae449f21f6a2c0a037ab2affe6
|
22.179
|
5.13 Security
|
[R-5.13-001] Void
[R-5.13-002] Void
[R-5.13-003] Void
[R-5.13-004] Void
[R-5.13-005] Void
[R-5.13-006] Void
[R-5.13-007] Void
[R-5.13-008] Void
[R-5.13-009] Void
[R-5.13-010] Void
[R-5.13-011] Void
[R-5.13-012] Void
[R-5.13-013] Void
|
025654ae449f21f6a2c0a037ab2affe6
|
22.179
|
5.14 Audio / voice quality
|
[R-5.14-001] Void
[R-5.14-002] MOS-LQO shall achieve the noise reduction performance of TIA-102.BABG [10] Table 3-1.
[R-5.14-003] MOS-LQO shall achieve a noise reduction performance for the 3GPP Adaptive Multi-Rate Wide Band codec (AMR-WB TS 26.190 [11] and TS 26.194 [12] that is equal to or greater than that specified for the P25 full rate and half rate voice codecs in TIA-102. BABG [10].
|
025654ae449f21f6a2c0a037ab2affe6
|
22.179
|
5.15 Interactions between MCPTT Group calls and MCPTT Private Calls (with Floor control)
|
[R-5.15-001] The MCPTT Service shall allow an MCPTT UE to be transmitting in one MCPTT Group Call while simultaneously receiving transmissions from one or more MCPTT Private Calls (with Floor control).
[R-5.15-002] The MCPTT Service shall allow an MCPTT UE to be receiving or transmitting in one MCPTT Private Call (with Floor control) while simultaneously receiving transmissions from one or more MCPTT Group Calls.
[R-5.15-003] The MCPTT Service shall allow an MCPTT UE to be receiving one or more MCPTT Group Calls while simultaneously receiving transmissions from one or more MCPTT Private Calls (with Floor control).
|
025654ae449f21f6a2c0a037ab2affe6
|
22.179
|
5.16 Relay requirements
|
[R-5.16-001] Void
[R-5.16-002] Void
[R-5.16-003] Void
|
025654ae449f21f6a2c0a037ab2affe6
|
22.179
|
5.17 Gateway requirements
|
[R-5.17-001] Void
|
025654ae449f21f6a2c0a037ab2affe6
|
22.179
|
5.18 Control and management by Mission Critical Organizations
| |
025654ae449f21f6a2c0a037ab2affe6
|
22.179
|
5.18.1 Overview
|
Subclause 5.18 contains general requirements for management of the MCPTT Service by Mission Critical Organizations sharing the same MCPTT system, and more specific requirements pertaining to management controls and operational visibility, and to management of security services.
|
025654ae449f21f6a2c0a037ab2affe6
|
22.179
|
5.18.2 General requirements
|
[R-5.18.2-001] Void
[R-5.18.2-002] Void
[R-5.18.2-003] Void
[R-5.18.2-004] Void
[R-5.18.2-005] Void
|
025654ae449f21f6a2c0a037ab2affe6
|
22.179
|
5.18.3 Operational visibility for Mission Critical Organizations
|
[R-5.18.3-001] Void
|
025654ae449f21f6a2c0a037ab2affe6
|
22.179
|
5.19 General Administrative – groups and users
|
[R-5.19-001] Void
[R-5.19-002] Void
[R-5.19-003] Void
[R-5.19-004] Void
[R-5.19-005] Void
[R-5.19-006] Void
[R-5.19-007] Void
[R-5.19-008] Void
|
025654ae449f21f6a2c0a037ab2affe6
|
22.179
|
6 MCPTT Service requirements specific to on-network use
| |
025654ae449f21f6a2c0a037ab2affe6
|
22.179
|
6.1 General administrative – groups and users
|
[R-6.1-001] Void
[R-6.1-002] Void
[R-6.1-003] Void
[R-6.1-004] Void
[R-6.1-005] Void
[R-6.1-006] Void
[R-6.1-007] Void
|
025654ae449f21f6a2c0a037ab2affe6
|
22.179
|
6.2 MCPTT calls
| |
025654ae449f21f6a2c0a037ab2affe6
|
22.179
|
6.2.1 Commencement modes for MCPTT Group calls
|
[R-6.2.1-001] The MCPTT Service shall be capable of allowing an MCPTT Group call setup request to proceed without prior acknowledgement by any MCPTT User of that MCPTT Group.
[R-6.2.1-001a] The MCPTT Service shall be capable of allowing an MCPTT Group Call setup request to proceed only if a minimum number of MCPTT Group Members are currently affiliated.
[R-6.2.1-001b] The MCPTT Service shall be capable of allowing an MCPTT Group Call setup request to proceed only if specific MCPTT Group Member(s) are currently affiliated.
[R-6.2.1-002] An MCPTT User currently affiliated to an MCPTT Group shall acknowledge receipt of an MCPTT Group call setup request, if requested to do so by the MCPTT Service.
[R-6.2.1-003] The MCPTT User's acknowledgement may require direct interaction of the MCPTT UE with the human user, or may be automatically executed by the MCPTT UE, in accordance with policy established by an MCPTT Administrator.
[R-6.2.1-004] The MCPTT Service shall be capable of requiring that a minimum number of Affiliated MCPTT Group Members acknowledges receipt of the MCPTT Group call setup request before the audio transmission proceeds.
[R-6.2.1-005] The MCPTT Service shall be capable of requiring that specific MCPTT Users acknowledge receipt of the MCPTT Group call setup request before the audio transmission proceeds, regardless of the affiliation state of those users.
NOTE 1: In this case the MCPTT Service affiliates the specific MCPTT Users who are not currently affiliated to the target MCPTT Group and then returns them to their previous affiliation state when the transmission ends.
[R-6.2.1-006] The MCPTT Service shall be capable of requiring that all MCPTT Users that are both affiliated to the MCPTT Group and in a given geographical area acknowledge receipt of an MCPTT Group call setup request before the audio transmission proceeds.
[R-6.2.1-007] The MCPTT Service shall provide a mechanism for an MCPTT Administrator to determine the subset of Affiliated MCPTT Group Members that shall acknowledge receipt of the MCPTT Group call setup request before the audio transmission proceeds.
NOTE 2: In the following requirements, the term, "MCPTT Group Call setup request requires acknowledgement" is used when one or more of the acknowledgement conditions defined above (i.e., [R-6.2.1-004], [R-6.2.1-005], [R-6.2.1-006], and/or [R-6.2.1-007]) applies.
[R-6.2.1-008] If an MCPTT Group Call setup request requires acknowledgement from Affiliated MCPTT Group Members, and the required MCPTT Group Members do not acknowledge the call setup within a configured time (the "acknowledged call setup timeout"), the MCPTT Service may proceed with the call and then may notify the initiating MCPTT User that the acknowledgements did not include all required members.
[R-6.2.1-009] If an MCPTT Group Call setup request requires acknowledgement from Affiliated MCPTT Group Members, and the required MCPTT Group Members do not acknowledge the call setup within a configured time, the MCPTT Service may abandon the call and then may notify the initiating MCPTT User that the acknowledgements did not include all required members.
[R-6.2.1-010] If an MCPTT Group Call setup request requires acknowledgement from Affiliated MCPTT Group Members, the initiating MCPTT User shall at any time have the option of allowing the call to proceed regardless of the state of the acknowledgements (i.e., to "convert" the call to an unacknowledged call).
[R-6.2.1-010a] If an MCPTT Group Call setup request requires acknowledgement from Affiliated MCPTT Group Members, and the required MCPTT Group Members did not acknowledge the call setup within a configured time, the MCPPT Service shall be able to provide the list of MCPTT Group Members who did not acknowledge the call to the initiating MCPTT User.
[R-6.2.1-011] If an MCPTT Group Call setup request requires acknowledgement from Affiliated MCPTT Group Members, the acknowledged call setup timeout shall be established by an MCPTT Administrator.
[R-6.2.1-012] If an MCPTT Group Call setup request requires acknowledgement from Affiliated MCPTT Group Members, the behaviour in response to the expiration of the acknowledged call setup timeout shall be established by an MCPTT Administrator.
[R-6.2.1-013] If an MCPTT Group Call setup request requires acknowledgement from Affiliated MCPTT Group Members, the MCPTT Service shall support an indefinite (i.e., infinite) call setup timeout.
[R-6.2.1-014] If the MCPTT Service has knowledge that some affiliated members of a group can not be Participants in an unacknowledged MCPTT Group Call, the MCPTT Service shall provide an indication to the requester that the call is proceeding without all affiliated members, and shall provide the list of the missing members based on policy established by the MCPTT Administrator.
[R-6.2.1-015] If MCPTT User(s) are excluded from an MCPTT call as there is insufficient capacity to support their participation the MCPTT Service shall ensure that the MCPTT User(s) receive a notification that they have been excluded from the call for reasons of lack of capacity.
|
025654ae449f21f6a2c0a037ab2affe6
|
22.179
|
6.2.2 Queuing
|
[R-6.2.2-001] Void
[R-6.2.2-002] Void
[R-6.2.2-003] Void
[R-6.2.2-004] Void
[R-6.2.2-005] Void
[R-6.2.2-006] Void
|
025654ae449f21f6a2c0a037ab2affe6
|
22.179
|
6.2.3 Floor control
| |
025654ae449f21f6a2c0a037ab2affe6
|
22.179
|
6.2.3.1 General aspects
|
[R-6.2.3.1-001] The Floor control functionality in an MCPTT Service shall determine at a point in time which Participant(s) are allowed to transmit to other Participant(s).
[R-6.2.3.1-002] Receiving Participant(s) shall receive audio from one transmitting Participant. The only exception is if an MCPTT Group is configured to allow simultaneous Transmitting MCPTT Group Members in override.
[R-6.2.3.1-003] The MCPTT Service shall provide a mechanism for the MCPTT Administrator to configure the number (maximum of N9) of simultaneous audios received by an MCPTT User in a single MCPTT Group.
|
025654ae449f21f6a2c0a037ab2affe6
|
22.179
|
6.2.3.2 Requesting permission to transmit
|
[R-6.2.3.2-001] An authorized Participant shall be able to request to transmit to an MCPTT Group or an individual Participant.
[R-6.2.3.2-002] At call setup the MCPTT Service shall provide a notification, for example audio and/or visual, to the MCPTT Group Member attempting to transmit that there are no other Group Members who have affiliated to the MCPTT Group.
[R-6.2.3.2-003] The Floor control functionality shall determine the transmitting Participant(s) when there are simultaneous requests for permission to transmit within the same call.
[R-6.2.3.2-004] Following an MCPTT Request for permission to transmit on the Selected MCPTT Group, the Affiliated MCPTT Group Member that made and was granted the request shall be given an indication of being allowed to transmit.
[R-6.2.3.2-005] Following an MCPTT Request for permission to transmit on the Selected MCPTT Group, an Affiliated MCPTT Group Member that made and was not granted the request shall be given an indication that permission to transmit was rejected or queued.
[R-6.2.3.2-006] The depth of the Floor control queue shall be configurable.
[R-6.2.3.2-007] Following an MCPTT Private Call (with Floor control) request for permission to transmit, the MCPTT User that is allowed to transmit shall be given an indication that the user is allowed to transmit to the targeted MCPTT User.
[R-6.2.3.2-008] Following an MCPTT Private Call (with Floor control) request for permission to transmit, an MCPTT User that is not allowed to transmit shall be given an indication that the permission to transmit was rejected or queued.
[R-6.2.3.2-009] The MCPTT Service shall provide an indication to receiving Participants that the transmitting Participant is starting to transmit.
[R-6.2.3.2-010] The MCPTT Service shall provide a mechanism for an MCPTT Participant to remove its MCPTT Request from the Floor control queue.
[R-6.2.3.2-011] The MCPTT Service shall provide a mechanism for removal (i.e., request accepted, request denied, or expiration of a timer) of an MCPTT Request from the Floor control queue.
[R-6.2.3.2-012] The MCPTT Service shall provide a mechanism for the MCPTT Administrator to configure the parameter(s) of the Floor control queue for an MCPTT Group (i.e., timer).
|
025654ae449f21f6a2c0a037ab2affe6
|
22.179
|
6.2.3.3 Override
| |
025654ae449f21f6a2c0a037ab2affe6
|
22.179
|
6.2.3.3.1 General aspects
|
[R-6.2.3.3.1-001] The MCPTT Service shall enable MCPTT Administrators to create a priority hierarchy for determining what Participants, Participant types, and urgent transmission types shall be granted a request to override an active MCPTT transmission.
[R-6.2.3.3.1-002] The MCPTT Service shall enable an MCPTT Administrator to configure which MCPTT Group transmission a Participant(s) receives, overriding and/or overridden for cases where an authorized Participant overrides an MCPTT transmission.
[R-6.2.3.3.1-003] The MCPTT Service shall enable the MCPTT Administrator to configure the MCPTT Group to allow only the overriding Participant to transmit or to allow both the overriding and overridden Participant to transmit.
[R-6.2.3.3.1-004] The MCPTT Service shall provide a mechanism for an MCPTT Administrator to configure MCPTT Private Calls (with Floor control) to allow only the overriding Participant to transmit or to allow both the overriding and overridden Participant to transmit.
[R-6.2.3.3.1-005] The priority hierarchy used for granting a request to override an active MCPTT transmission shall contain at least four (4) levels.
[R-6.2.3.3.1-006] The transmitting Participant shall be determined by the relative Floor control priorities of the Participants and Call type based on priority (e.g MCPTT Emergency).
[R-6.2.3.3.1-007] The MCPTT Service shall provide a mechanism for Participants, to override an active MCPTT transmission of a transmitting Participant when the priority level of the overriding Participant or Call type based on priority (e.g MCPTT Emergency) are ranked higher than the priority level of the transmitting Participant or Call type based on priority.
[R-6.2.3.3.1-008] If an authorized Participant overrides an MCPTT transmission, the MCPTT Service shall provide a means of notifying the overridden Participant(s) that the transmission has been overridden.
|
025654ae449f21f6a2c0a037ab2affe6
|
22.179
|
6.2.3.3.2 Override – one transmitting Participant
|
[R-6.2.3.3.2-001] If the MCPTT Group has been configured to only allow the overriding transmitting Participant, the MCPTT Service shall revoke the transmit permission of the overridden transmitting Participant.
|
025654ae449f21f6a2c0a037ab2affe6
|
22.179
|
6.2.3.3.3 Override – simultaneously Transmitting MCPTT Group Members
|
[R-6.2.3.3.3-001] If the MCPTT Group has been configured to allow both overriding and overridden transmitting Participants, authorized receiving Participants shall be enabled to listen to both the overriding and overridden Participant transmissions, dependent on configuration.
[R-6.2.3.3.3-002] The MCPTT Service shall allow successive overrides of an MCPTT Group Call when the request to override is made by an MCPTT User having a higher Floor control priority than the currently transmitting Participants.
[R-6.2.3.3.3-003] In the case of successive overrides, the MCPTT Service shall enable only two transmissions, one overriding transmission, from the highest priority MCPTT User, and one overridden transmission, chosen from among the two overridden Participants based upon configured rule(s). (i.e., this could be based simply on priority of user, it could be based on a policy that an overridden MCPTT Emergency transmission shall remain as the overridden transmission or a rule could be established that the MCPTT system shall not allow two dispatchers to be both the overriding and overridden transmitters.).
|
025654ae449f21f6a2c0a037ab2affe6
|
22.179
|
6.2.3.4 Terminating permission to transmit
|
[R-6.2.3.4-001] The MCPTT Service shall enable an authorized MCPTT User to terminate the permission to transmit of a transmitting Participant at any time.
[R-6.2.3.4-002] A transmitting Participant shall be able to indicate to the MCPTT Service that the Participant no longer wants to transmit.
NOTE: In this case audio stops being transmitted to the receiver Participant(s) until an authorized Participant sends a subsequent request for permission to transmit.
[R-6.2.3.4-003] The MCPTT Service shall provide an indication to receiving Participants that the transmitting Participant has finished transmitting.
|
025654ae449f21f6a2c0a037ab2affe6
|
22.179
|
6.2.3.5 Transmit time limit
|
[R-6.2.3.5-001] The MCPTT Service shall enable an MCPTT Administrator to configure the limit for the length of time that a Participant transmits from a single request to transmit.
[R-6.2.3.5-002] The Floor control functionality shall have a configurable limit for the length of time that a Participant transmits from a single request to transmit.
[R-6.2.3.5-003] The Floor control functionality shall provide an indication to the transmitting Participant that the Participant is within a configurable amount of time before his transmit time limit is reached.
[R-6.2.3.5-004] The Floor control functionality shall provide an indication to the transmitting Participant that the Participant's transmit time limit has been reached.
[R-6.2.3.5-005] The Floor control functionality shall remove the permission to transmit from the transmitting Participant when the Participant's transmit time limit has been reached.
|
025654ae449f21f6a2c0a037ab2affe6
|
22.179
|
6.2.3.6 Audio cut-in on designated MCPTT Groups
| |
025654ae449f21f6a2c0a037ab2affe6
|
22.179
|
6.2.3.6.1 Overview
|
The audio cut-in feature applies to specially designated MCPTT Groups and results in Floor control for that group allowing any participant within the MCPTT Group to interrupt any other participant. In particular the audio cut-in feature means that the last Participant to request the floor is assigned the floor immediately and there is only ever one talker on the call at a particular point in time. Audio cut-in is often used for teams escorting VIPs where timeliness is essential to allow teams to react as quickly as possible.
Other than the difference in floor control logic, the MCPTT Groups configured to support audio cut-in behave in the same way as other MCPTT Groups with group management, affiliation, selection of a group, requesting the floor, the notifications received related to Floor control etc working in the same way.
|
025654ae449f21f6a2c0a037ab2affe6
|
22.179
|
6.2.3.6.2 Requirements
|
[R-6.2.3.6.2-001] The MCPTT Group shall be configurable to allow audio cut-in.
NOTE 1: MCPTT Groups configured for audio cut-in behave in the same way as MCPTT Groups not configured for audio cut-in in all other respects other than the Floor control logic described in this sub-clause.
[R-6.2.3.6.2-002] When an MCPTT Group has been configured to support audio cut-in, the Floor control functionality shall give the floor to the MCPTT Group Member that has selected that MCPTT Group and made the most recent request to transmit in that MCPTT Group.
NOTE 2: Requests to transmit that are received simultaneously will be addressed by manufacturer implementation.
[R-6.2.3.6.2-003] When an MCPTT Group has been configured to support audio cut-in the Floor control functionality shall restrict the number of talkers in the group to one.
[R-6.2.3.6.2-004] When an MCPTT Group has been designated to support audio cut-in the MCPTT Group shall not support any form of floor control queuing and associated functionality.
[R-6.2.3.6.2-005] When the current talker is interrupted by a request to transmit on an MCPTT Group supporting audio cut-in, the talk request of the interrupted talker shall end.
NOTE 3: The interrupted talker must make a new request to transmit in order to transmit again.
[R-6.2.3.6.2-006] Void
[R-6.2.3.6.2-007] Void
|
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.