hash stringlengths 32 32 | doc_id stringlengths 5 12 | section stringlengths 5 1.47k | content stringlengths 0 6.67M |
|---|---|---|---|
38055db1edaa9b8bf534dbc753cc4ba8 | 22.280 | 6.8.8.4 MCX Service Emergency Alert
| |
38055db1edaa9b8bf534dbc753cc4ba8 | 22.280 | 6.8.8.4.1 Requirements
| [R-6.8.8.4.1-001] The MCX Service may allow MCX UEs that are unauthorized, not registered, or authenticated to activate the MCX Service Emergency Alert capability.
[R-6.8.8.4.1-002] The MCX User shall be notified that the MCX Service Emergency Alert was received by the MCX Service.
[R-6.8.8.4.1-003] The MCX Service s... |
38055db1edaa9b8bf534dbc753cc4ba8 | 22.280 | 6.8.8.4.2 MCX Service Emergency Alert cancellation requirements
| [R-6.8.8.4.2-001] The MCX Service shall allow authorized users to cancel any MCX UE's MCX Service Emergency Alert from the system.
[R-6.8.8.4.2-002] The MCX Service shall provide a mechanism for an MCX Service Administrator to authorize a user to cancel, from the system, an MCX Service Emergency Alert initiated by ano... |
38055db1edaa9b8bf534dbc753cc4ba8 | 22.280 | 6.8.8.5 Ad hoc Group Communication requirements
| [R-8.8.8.5-001] The In-progress Emergency condition for a MCX Service Ad hoc Group Communication shall be cancelled when the communication is terminated.
|
38055db1edaa9b8bf534dbc753cc4ba8 | 22.280 | 6.9 IDs and aliases
| [R-6.9-001] The MCX Service shall provide a mechanism for permanent and temporary assignment of IDs and aliases.
[R-6.9-002] The MCX Service shall provide a mechanism for the enforcement of uniqueness of IDs and aliases.
[R-6.9-003] The MCX Service shall provide a mechanism for an MCX Service Administrator to configu... |
38055db1edaa9b8bf534dbc753cc4ba8 | 22.280 | 6.10 MCX Service User Profile management
| [R-6.10-001] The MCX Service shall be able to dynamically modify one or more pieces of information within the MCX Service User Profile (e.g., the list of MCX Service Groups for which the user has access credentials) while in use by the MCX User.
[R-6.10-002] The MCX Service shall provide a means by which an MCX Servic... |
38055db1edaa9b8bf534dbc753cc4ba8 | 22.280 | 6.11 Support for multiple devices
| [R-6.11-001] The MCX Service shall provide a notification to the MCX User if the MCX User is already logged on to another MCX UE.
[R-6.11-002] The MCX Service shall provide the mechanisms to allow an MCX User to log off remotely from other MCX UEs.
[R-6.11-003] The MCX Service shall provide the mechanism to allow an ... |
38055db1edaa9b8bf534dbc753cc4ba8 | 22.280 | 6.12 Location
| [R-6.12-001] The MCX Service shall provide Location information of the transmitting MCX UE to receiving MCX UEs subject to privacy restrictions.
[R-6.12-002] The MCX Service shall support conveyance of Location information provided by 3GPP location services.
[R-6.12-003] The MCX Service shall provide a means for an a... |
38055db1edaa9b8bf534dbc753cc4ba8 | 22.280 | 6.13 Security
| |
38055db1edaa9b8bf534dbc753cc4ba8 | 22.280 | 6.13.1 Overview
| Security covers areas designed to protect the confidentiality, integrity, and availability of information that is processed, stored, and transmitted. The security requirements listed here cover the areas of cryptographic protocols, authentication, access control, regulatory issues and storage control.
|
38055db1edaa9b8bf534dbc753cc4ba8 | 22.280 | 6.13.2 Cryptographic protocols
| [R-6.13.2-001] The MCX Service shall employ open cryptographic standards, subject to applicable local policy (e.g., Federal Information Processing Standards (FIPS) 140-2).
[R-6.13.2-002] The MCX Service shall allow for update to new cryptographic operations and methods without making obsolete existing operations and m... |
38055db1edaa9b8bf534dbc753cc4ba8 | 22.280 | 6.13.3 Authentication
| [R-6.13.3-001] The MCX Service shall provide a means by which an MCX UE can require authentication of the MCX Service.
|
38055db1edaa9b8bf534dbc753cc4ba8 | 22.280 | 6.13.4 Access control
| [R-6.13.4-001] The MCX Service shall support suspending or disabling of access from an MCX UE or an MCX User to the MCX Service.
[R-6.13.4-002] An MCX User who has a profile that has been deleted or suspended shall be prevented from using that MCX Service User Profile to access the MCX Service.
[R-6.13.4-003] The MCX... |
38055db1edaa9b8bf534dbc753cc4ba8 | 22.280 | 6.13.5 Regulatory issues
| [R-6.13.5-001] The MCX Service shall support lawful interception.
6.13.6 Storage control
[R-6.13.6-001] The MCX Service shall provide all relevant security for media storage (e.g., video or data) on the MCX UE (e.g., data encryption, access only to authorized MCX Group Members).
|
38055db1edaa9b8bf534dbc753cc4ba8 | 22.280 | 6.14 Interactions for MCX Service Group Communications and MCX Service Private Communications
| [R-6.14-001] The MCX Service shall allow an MCX UE to be receiving and transmitting in one MCX Private Communication (without Floor control) while simultaneously receiving transmissions from other MCX Group communications within the same MCX service.
[R-6.14-002] The MCX Service shall allow an MCX UE to be receiving a... |
38055db1edaa9b8bf534dbc753cc4ba8 | 22.280 | 6.15 Additional services for MCX Service communications
| |
38055db1edaa9b8bf534dbc753cc4ba8 | 22.280 | 6.15.1 Discreet listening capabilities
| [R-6.15.1-001a] The MCX Service shall provide discreet listening capabilities without noticeable impact on or knowledge of the target MCX User, or the members of the target MCX Service Group including Ad hoc groups, and all other unauthorized MCX Users.
[R-6.15.1-001] The MCX Service shall provide a mechanism for an ... |
38055db1edaa9b8bf534dbc753cc4ba8 | 22.280 | 6.15.2 Ambient listening
| 6.15.2.1 Overview of ambient listening
Ambient listening is a feature that allows an authorized MCX User, typically a dispatcher, to cause an MCX UE to initiate a communication which results in no indication on the MCX UE that it is transmitting. Ambient listening can be initiated by an authorized MCX User who wants ... |
38055db1edaa9b8bf534dbc753cc4ba8 | 22.280 | 6.15.2.2 Ambient listening requirements
| |
38055db1edaa9b8bf534dbc753cc4ba8 | 22.280 | 6.15.2.2.1 General ambient listening requirements
| [R-6.15.2.2.1-001] The MCX UE that is being listened to shall be the only transmitting party in the Private Communication.
[R-6.15.2.2.1-002] For an MCX UE that is being listened to there shall be no indication on the MCX UE that it is transmitting.
[R-6.15.2.2.1-003] If someone attempts to turn off an MCX UE that is... |
38055db1edaa9b8bf534dbc753cc4ba8 | 22.280 | 6.15.2.2.2 Remotely initiated ambient listening requirements
| [R-6.15.2.2.2-001] The MCX Service shall provide a mechanism to allow an MCX Service Administrator and/or an authorized user to set up Ambient Listening on a remote MCX UE within their authority.
[R-6.15.2.2.2-002] The MCX Service shall ensure that Ambient Listening triggered remotely is terminated only by the remote ... |
38055db1edaa9b8bf534dbc753cc4ba8 | 22.280 | 6.15.2.2.3 Locally initiated ambient listening requirements
| [R-6.15.2.2.3-001] The MCX Service shall provide a mechanism to allow an authorized MCX User to use the MCX UE that the MCX User is currently using to initiate Ambient Listening to another authorized MCX User (e.g., a dispatcher).
[R-6.15.2.2.3-002] The MCX Service shall ensure that Ambient Listening triggered locally... |
38055db1edaa9b8bf534dbc753cc4ba8 | 22.280 | 6.15.3 Remotely initiated MCX Service Communication
| |
38055db1edaa9b8bf534dbc753cc4ba8 | 22.280 | 6.15.3.1 Overview
| A Remotely initiated MCX Service Communication is a feature that allows an authorized user, typically a dispatcher, to cause a remote MCX UE to initiate a communication by itself, without its user explicitly initiating the communication manually. The purpose of this feature allows the dispatcher to "listen" to activiti... |
38055db1edaa9b8bf534dbc753cc4ba8 | 22.280 | 6.15.3.2 Requirements
| [R-6.15.3.2-001] The MCX Service shall provide a mechanism for an MCX Service Administrator and/or authorized MCX User to cause an MCX UE that is within their authority to initiate an MCX Private Communication to the MCX Service Administrator and/or authorized MCX User and then begin transmitting to the MCX Service Adm... |
38055db1edaa9b8bf534dbc753cc4ba8 | 22.280 | 6.15.4 Recording and audit requirements
| [R-6.15.4-001] The MCX Service shall provide a mechanism for a Mission Critical Organization to log the metadata of the MCX Service Group Communications and MCX Service Private Communications under the organization's authority.
[R-6.15.4-002] Metadata shall be logged for both the transmitting Participant and the recei... |
38055db1edaa9b8bf534dbc753cc4ba8 | 22.280 | 6.15.5 MCX Service Ad hoc Group Communication
| |
38055db1edaa9b8bf534dbc753cc4ba8 | 22.280 | 6.15.5.1 Overview
| Due to an incident in an area, or a special operation, it can be necessary to coordinate MCX Users using Group Communication where these users do not normally work together and do not share any groups in common. MCX Service Ad hoc Group Communication enables authorized users to combine a random set of MCX Users into a ... |
38055db1edaa9b8bf534dbc753cc4ba8 | 22.280 | 6.15.5.2 General aspects
| [R-6.15.5.2-001] The MCX Service shall provide a mechanism for an authorized MCX User to combine an ad hoc multiplicity of MCX Users into a MCX Service Ad hoc Group Communication. The MCX Users in the participants list may be identified by their MCX Service ID or by their Functional Alias.
NOTE: Selection of the list ... |
38055db1edaa9b8bf534dbc753cc4ba8 | 22.280 | 6.15.5.3 Administrative
| [R-6.15.5.3-001] The MCX Service shall provide a mechanism for an MCX Service Administrator to configure which MCX Users, within their authority, are authorized to initiate and/or release a MCX Service Ad hoc Group Communication.
[R-6.15.5.3-002] The MCX Service shall provide a mechanism for an MCX Service Administra... |
38055db1edaa9b8bf534dbc753cc4ba8 | 22.280 | 6.15.5.4 Notification and acknowledgement for MCX Service Ad hoc Group Communications
| [R-6.15.5.4-001] The MCX Service shall provide mechanisms for notification and acknowledgement of MCX Service Ad hoc Group Communications as defined in section 6.2.1.
[R-6.15.5.4-001a] The notification and acknowledgement shall include the corresponding Functional Alias for each MCService ID, if available.
NOTE: For... |
38055db1edaa9b8bf534dbc753cc4ba8 | 22.280 | 6.15.6 MCX Service Ad hoc Group Emergency Alert
| |
38055db1edaa9b8bf534dbc753cc4ba8 | 22.280 | 6.15.6.1 Overview
| Due to an incident in an area, or a special operation, it can be necessary to coordinate MCX Users using Ad hoc Group Emergency Alert where these users do not normally work together and do not share any groups in common. MCX Service Ad hoc Group Emergency Alert enables authorized users to combine a random set of MCX Us... |
38055db1edaa9b8bf534dbc753cc4ba8 | 22.280 | 6.15.6.2 General aspects
|
R-6.15.6.2-001
R-6.15.6.2-002
R-6.15.6.2-002a
R-6.15.6.2-003
R-6.15.6.2-004
R-6.15.6.2-005
R-6.15.6.2-005b
R-6.15.6.2-006
R-6.15.6.2-007
R-6.15.6.2-008
R-6.15.6.2-009
R-6.15.6.2-010
6.15.6.3 Administrative
R-6.15.6.3-001
R-6.15.6.3-002
R-6.15.6.3-003
R-6.15.6.3-004
R-6.15.6.3-005
R-6.15.6.3-... |
38055db1edaa9b8bf534dbc753cc4ba8 | 22.280 | 6.15.6.3 Administrative
| [R-6.15.6.3-001] The MCX Service shall provide a mechanism for an MCX Service Administrator to configure which MCX Users, within their authority, are authorized to initiate a MCX Service Ad hoc Group Emergency Alert.
[R-6.15.6.3-002] The MCX Service shall provide a mechanism for an MCX Service Administrator to config... |
38055db1edaa9b8bf534dbc753cc4ba8 | 22.280 | 6.15.6.4 Notification and acknowledgement for MCX Service Ad hoc Group Emergency Alert
| [R-6.15.6.4-001] The MCX Service shall provide mechanisms for notification and acknowledgement of MCX Service Ad hoc Group Emergency Alert, including for each MC ServiceID the corresponding Functional Alias, if available.
[R-6.15.6.4-002] The MCX Service shall provide notifications to the relevant participants and aut... |
38055db1edaa9b8bf534dbc753cc4ba8 | 22.280 | 6.16 Interaction with telephony services
| [R-6.16-001] The MCX Service shall provide a mechanism to allow an MCX Service Administrator to configure whether an MCX User using an MCX UE is able to make and/or receive telephony calls, including public emergency calls.
[R-6.16-002] The MCX Service shall provide a mechanism for an MCX User authorized to use teleph... |
38055db1edaa9b8bf534dbc753cc4ba8 | 22.280 | 6.17 Interworking
| |
38055db1edaa9b8bf534dbc753cc4ba8 | 22.280 | 6.17.1 Non-3GPP access
| [R-6.17.1-001] Subject to security and operational constraints and limitations of the underlying access technology, the MCX Service shall provide a mechanism to allow IP-based non-3GPP access to the MCX Service system.
NOTE: An example of non-3GPP access is a dispatcher connecting to the system via a console.
|
38055db1edaa9b8bf534dbc753cc4ba8 | 22.280 | 6.17.2 Interworking between MCX Service systems
| [R-6.17.2-001] An MCX Service shall provide mechanisms to allow an MCX User to operate in a Partner MCX Service System, subject to authorization from both the Partner and the Primary MCX Service Systems of the MCX User.
[R-6.17.2-002] The authentication of an MCX User with an MCX Service in a Partner MCX Service Syste... |
38055db1edaa9b8bf534dbc753cc4ba8 | 22.280 | 6.17.3 Interworking with non-MCX Service systems
| |
38055db1edaa9b8bf534dbc753cc4ba8 | 22.280 | 6.17.3.1 GSM-R
| [R-6.17.3.1-001] The MCX Service system shall enable bilateral interworking for MCX User positioning information and location information provided for a GSM-R mobile station [9], [10].
[R-6.17.3.1-002] The MCX Service system shall enable interworking with a GSM-R system that is compliant with the UIC GSM-R (EIRENE) s... |
38055db1edaa9b8bf534dbc753cc4ba8 | 22.280 | 6.17.3.2 External systems
| [R.6.17.3.2-001] The MCX Service system shall support a mechanism for the MCX Service Administrator to also allow the usage of functional alias and/or MCX User Identity as addressing scheme for use by non-MCX services (e.g. Machine Type Communication).
[R.6.17.3.2-002] The MCX Service system shall enable interworking ... |
38055db1edaa9b8bf534dbc753cc4ba8 | 22.280 | 6.18 MCX Service coverage extension using ProSe UE-to-Network Relays
| [R-6.18-001] A ProSe-enabled UE authorized to act as a ProSe UE-to-Network Relay shall, if authorized, support the bi-directional relay of signalling (control plane) and data (user plane) between an MCX UE and the on-network MCX Service.
[R-6.18-002] A ProSe UE-to-Network Relay authorized to act as an MCX Service rela... |
38055db1edaa9b8bf534dbc753cc4ba8 | 22.280 | 6.19 Additional MCX Service requirements
| |
38055db1edaa9b8bf534dbc753cc4ba8 | 22.280 | 6.19.1 Communication rejection and queuing
| Requests to transmit appear in MCX Services in many forms and under many circumstances. Normally, requests to transmit are accompanied by priority information that is used to arbitrate the decision to assign resources for the transmission amongst competing requests to transmit. Upon arrival, a request to transmit is ... |
38055db1edaa9b8bf534dbc753cc4ba8 | 22.280 | 6.19.1.1 Requirements
| [R-6.19.1.1-001] The MCX Service shall provide a mechanism to queue any MCX request to transmit.
[R-6.19.1.1-002] The MCX Service shall provide a mechanism to reject MCX request to transmit with a cause indication.
[R-6.19.1.1-003] The MCX Service shall notify the requesting MCX Participant and may notify one or mor... |
38055db1edaa9b8bf534dbc753cc4ba8 | 22.280 | 7 MCX Service requirements specific to off-network use
| |
38055db1edaa9b8bf534dbc753cc4ba8 | 22.280 | 7.1 Off-network communications overview
| The MCX Service while operating in off-network mode comprises a set or collection of functions necessary to provide Mission Critical Services (e.g., MCPTT, MCVideo, MCData, etc.) using a ProSe direct (UE-to-UE) Communication path (ProSe direct communication path) for transport. The ProSe direct communication path does ... |
38055db1edaa9b8bf534dbc753cc4ba8 | 22.280 | 7.2 General off-network MCX Service requirements
| [R-7.2-001] In order to operate off the network using the direct communication path, an MCX UE shall be a Public Safety ProSe-enabled UE.
[R-7.2-002] The Off-Network MCX Service shall make use of the ProSe capabilities related to ProSe Communication using the direct communication path between Public Safety ProSe-enabl... |
38055db1edaa9b8bf534dbc753cc4ba8 | 22.280 | 7.3 Admission control
| |
38055db1edaa9b8bf534dbc753cc4ba8 | 22.280 | 7.3.1 General aspects
| [R-7.3.1-001] The admission control functionality shall authorize a participant to start a communication.
[R-7.3.1-002] The admission control function shall be common to all services. That is to say resources are shared by all MCX Services depending on priorities. When a new communication is started an MCX service sha... |
38055db1edaa9b8bf534dbc753cc4ba8 | 22.280 | 7.4 Communication termination
| [R-7.4-001] The MCX Service when operating off the network shall provide a mechanism for an MCX Service Administrator to preconfigure separately the limit for the total length of time of an MCX Service Group Communication and an MCX Service Private Communication.
[R-7.4-002] The MCX Service when operating off the netw... |
38055db1edaa9b8bf534dbc753cc4ba8 | 22.280 | 7.5 Broadcast Group
| [R-7.5-001] The MCX Service when operating off the network shall support Broadcast Group Communications within that MCX Service.
[R-7.5-002] The MCX Service shall deliver an off-Network Broadcast Group Communication to the members of a Broadcast Group within that MCX Service who are within communication range, and who... |
38055db1edaa9b8bf534dbc753cc4ba8 | 22.280 | 7.6 MCX Service priority requirements
| [R-7.6-001] The Off-Network MCX Service shall assign to each MCX Service Group or Private Communication:
- an application layer pre-emption capability;
- a capability to be pre-empted; and
- an application layer priority value.
[R-7.6-002] The Off-Network MCX Service shall support at least 8 configurable levels of ... |
38055db1edaa9b8bf534dbc753cc4ba8 | 22.280 | 7.7 Communication types based on priorities
| |
38055db1edaa9b8bf534dbc753cc4ba8 | 22.280 | 7.7.1 MCX Service Emergency Group Communication requirements
| [R-7.7.1-001] The Off-Network MCX Service shall provide a mechanism for an authorized Participant of an off-network MCX Service Group Communication to change the status of the off-network MCX Service Group Communication in progress to an off-network MCX Service Emergency Group Communication.
[R-7.7.1-002] An off-netwo... |
38055db1edaa9b8bf534dbc753cc4ba8 | 22.280 | 7.7.2 MCX Service Emergency Group Communication cancellation requirements
| [R-7.7.2-001] An indication of the cancellation of an off-network MCX Service Emergency Communication and the identity of the cancelling user shall be transmitted to Affiliated MCX Service Group Members of the off-network MCX Service Emergency Group Communication.
|
38055db1edaa9b8bf534dbc753cc4ba8 | 22.280 | 7.7.3 Imminent Peril Communication
| 7.7.3.1 Imminent Peril Group Communication requirements
[R-7.7.3.1-001] The Off-Network MCX Service shall provide a mechanism for an Affiliated MCX Service Group Member to initiate (or join) an off-network MCX Service Group Communication and set (or change) the status of the communication to Imminent Peril.
[R-7.7.... |
38055db1edaa9b8bf534dbc753cc4ba8 | 22.280 | 7.8 Location
| [R-7.8-001] An MCX UE shall be capable of transmitting its Location, if known, to other MCX UEs when operating off the network, subject to privacy restrictions.
[R-7.8-002] An MCX UE shall be capable of providing a mechanism for obtaining the distance between the MCX UE and other MCX UEs within communication range.
[... |
38055db1edaa9b8bf534dbc753cc4ba8 | 22.280 | 7.9 Security
| [R-7.9-001] MCX UEs operating off the network shall be capable of protecting the confidentiality of Location and identity information conveyed to or from other MCX UEs.
[R-7.9-002] MCX UEs operating off the network shall be capable of authenticating the sender of messages carrying Location and identity information.
|
38055db1edaa9b8bf534dbc753cc4ba8 | 22.280 | 7.10 Off-network MCX Service operations
| [R-7.10-001] Off-Network MCX Services shall be able to operate in the complete absence of any fixed infrastructure.
[R-7.10-002] Off-Network MCX Services shall only be available for authorized users.
[R-7.10-003] The MCX Service shall provide a mechanism for an MCX Service Administrator to authorize users for Off-Net... |
38055db1edaa9b8bf534dbc753cc4ba8 | 22.280 | 7.11 Off-network UE functionality
| [R-7.11-001] An MCX UE shall be capable of utilizing off-network MCX Service and on-network MCX Service at the same time.
NOTE: Sub-clause 7A.2 in TS 22.278 specifies requirements for concurrent communications on and off the network within the same group, concurrent communications on and off the network with different... |
38055db1edaa9b8bf534dbc753cc4ba8 | 22.280 | 7.12 Streaming for ProSe UE-to-UE Relay and UE-to-Network Relay
| |
38055db1edaa9b8bf534dbc753cc4ba8 | 22.280 | 7.12.1 UE-to-Network Relay for all data types
| [R-7.12.1-001] MCX Users shall be able to transmit and receive real time data (e.g., voice, streaming video/data) between an on-network MCX UE and an off-network MCX UE via a ProSe UE-to-Network relay using the MCX UE-to-Network Relay service.
[R-7.12.1-002] The MCX Service shall provide a mechanism for an authorized ... |
38055db1edaa9b8bf534dbc753cc4ba8 | 22.280 | 7.12.2 UE-to-UE Relay streaming
| [R-7.12.2-001] MCX Users shall be able to transmit and receive streaming video or data between an off-network MCX UE and another off-network MCX UE via a ProSe UE-to-UE relay using the MCX UE-to-UE Relay service.
[R-7.12.2-002] The MCX Service shall minimize the interruption to an on-going MCX Service communication wh... |
38055db1edaa9b8bf534dbc753cc4ba8 | 22.280 | 7.12.3 Off-Network streaming
| [R-7.12.3-001] MCX Users shall be able to transmit and receive streaming video or data between an off-network MCX UE and another off-network MCX UE via ProSe communications.
[R-7.12.3-002] The MCX Service shall minimize the interruption to an on-going MCX Service communication when an MCX UE transitions its connection... |
38055db1edaa9b8bf534dbc753cc4ba8 | 22.280 | 7.13 Switching to off-network MCX Service
| [R-7.13-001] An MCX UE shall be capable of automatically switching to a ProSe direct communications path for use of MCX Service when detecting an off-network (out of coverage) condition.
[R-7.13-002] A means shall be provided for an authorized MCX User to be able to manually switch between on-network operation and a P... |
38055db1edaa9b8bf534dbc753cc4ba8 | 22.280 | 7.14 Off-network recording and audit requirements
| [R-7.14-001] The Off-Network MCX Service shall provide a mechanism to collect metadata for MCX Service Group Communications and MCX Service Private Communications (e.g., initiating MCX Service User ID, MCX Service Group ID) and non-communication activities (e.g., changing group settings) from MCX UEs operating in off-n... |
38055db1edaa9b8bf534dbc753cc4ba8 | 22.280 | 7.15 Off-network UE-to-UE Relay
| |
38055db1edaa9b8bf534dbc753cc4ba8 | 22.280 | 7.15.1 Private Communications
| [R-7.15.1-001] The Off-Network MCX Service shall provide a means by which the MCX User of a (source) UE can make a Private Communication to the MCX User of a (target) UE via one or more ProSe UE-to-UE Relays.
[R-7.15.1-002] The Off-Network MCX Service shall provide a mechanism for a source MCX User to query whether a ... |
38055db1edaa9b8bf534dbc753cc4ba8 | 22.280 | 7.15.2 Group Communications
| [R-7.15.2-001] An MCX Service Administrator or authorized user shall be able to configure a ProSe-enabled UE, authorized to act as a ProSe UE-to-UE Relay, to relay any received MCX Service transmissions for one (or more) specified MCX Service Groups via one or more ProSe UE-to-UE Relays.
[R-7.15.2-002] An MCX UE recei... |
38055db1edaa9b8bf534dbc753cc4ba8 | 22.280 | 7.16 Off-network Ad hoc Group Communication
|
R-7.16-001
7.15.2 Group Communications
R-7.15.2-001
R-7.15.2-002
8 Inter-MCX Service interworking
NA
8.1 Inter-MCX Service interworking overview
NA
8.2 Concurrent operation of different MCX Services
NA
8.2.1 Overview
NA
8.2.2 ... |
38055db1edaa9b8bf534dbc753cc4ba8 | 22.280 | 8.1 Inter-MCX Service interworking overview
| Clause 8 describes interworking of one MCX Service with another.
The MCData Service as defined in TS 22.282 [3] includes description of multiple independent applications and data transfer capabilities, which may themselves be subject to interworking limitations as identified in clause 8. Therefore, requirements in cla... |
38055db1edaa9b8bf534dbc753cc4ba8 | 22.280 | 8.2 Concurrent operation of different MCX Services
| |
38055db1edaa9b8bf534dbc753cc4ba8 | 22.280 | 8.2.1 Overview
| In some cases, a User or UE will use multiple independent MCX Services. The intention in this case is that each service will operate totally independently of the other services and should not cause service, capability or capacity interaction problems. It is understood that different UE may have different abilities to c... |
38055db1edaa9b8bf534dbc753cc4ba8 | 22.280 | 8.2.2 Requirements
| [R-8.2.2-001] Except where expressly stated each MCX Service shall operate independently of each other MCX Service.
[R-8.2.2-002] Any floor control facility remains completely independent for each of simultaneous MCX Services except where expressly stated.
[R-8.2.2-003] A user shall be able to transmit on one MCX Ser... |
38055db1edaa9b8bf534dbc753cc4ba8 | 22.280 | 8.3 Use of unsharable resources within a UE
| [R-8.3-001] An MCX UE should be able to present audio from multiple sources (e.g. MCVideo, MCPTT) in a manner that is easily distinguished.
[R-8.3-002] An MCX UE may enable the user (e.g. incident commander) to control the relative volumes and spatial rendering of concurrent audio sources (e.g. MCVideo, MCPTT) at the ... |
38055db1edaa9b8bf534dbc753cc4ba8 | 22.280 | 8.4 Single group with multiple MCX Services
| |
38055db1edaa9b8bf534dbc753cc4ba8 | 22.280 | 8.4.1 Overview
| It is useful to be able to configure any single group to be able to handle multiple MCX Services. In sub-clause 8.4 requirements are on the service to provide a solution that looks as though the services are working in a coupled and coordinated manner. The exact means of achieving this is not implied here. So, where a ... |
38055db1edaa9b8bf534dbc753cc4ba8 | 22.280 | 8.4.2 Requirements
| [R-8.4.2-001] Mission critical groups shall be able to use multiple MCX Services independently or in combination.
[R-8.4.2-002] The MCX Service shall provide a mechanism by which an authorized MCX User can affiliate to a mission critical group using that MCX Service through a single logical group affiliation for any ... |
38055db1edaa9b8bf534dbc753cc4ba8 | 22.280 | 8.4.3 Compatibility of UE
| |
38055db1edaa9b8bf534dbc753cc4ba8 | 22.280 | 8.4.3.1 Advertising service capabilities required
| [R-8.4.3.1-001] The MCX Service shall provide a mechanism by which an MCX User of a UE can only affiliate to a Common MCX Service Group(s) for MCX Services that the MCX User’s UE is capable of supporting.
[R-8.4.3.1-002] The MCX Service shall provide a mechanism to advertise the service capabilities required to partic... |
38055db1edaa9b8bf534dbc753cc4ba8 | 22.280 | 8.4.3.2 Conversion between capabilities
| [R-8.4.3.2-001] Where an MCX Service does not advertise the service capabilities required to participate in a group it is assumed that service capability itself is sufficient to take part in the group. For example if a specific codec is being used and a joining UE may not support that codec then the service will provid... |
38055db1edaa9b8bf534dbc753cc4ba8 | 22.280 | 8.4.4 Individual permissions for service access
| [R-8.4.4-001] When a UE makes a combined request to affiliate to a Common MCX Service Group the MCX Service may respond by permitting access to the group for some but not all MCX Services if appropriate.
|
38055db1edaa9b8bf534dbc753cc4ba8 | 22.280 | 8.4.5 Common alias and user identities or mappable
| [R-8.4.5-001] To support combined services where the operation is intended to be coordinated, it shall be possible for one MCX Service to access and communicate using user identifying information in use for a coordinated MCX Service.
|
38055db1edaa9b8bf534dbc753cc4ba8 | 22.280 | 8.4.6 Single location message
| [R-8.4.6-001] The MCX Service shall provide configuration and capability so that when a UE is affiliated to a Common MCX Service Group and some or all of the MCX Services periodically require location messages to be sent then each location message sent may be configured to apply to all MCX Services or to only one speci... |
38055db1edaa9b8bf534dbc753cc4ba8 | 22.280 | 8.5 Priority between services
| |
38055db1edaa9b8bf534dbc753cc4ba8 | 22.280 | 8.5.1 Overview
| The 3GPP priority system using ARP and QCI is expected to be used for relative priority treatment among communications at the transport level. Further application of priority will be invoked in and by the MCX Service system according to service related requirements e. g User and situation
|
38055db1edaa9b8bf534dbc753cc4ba8 | 22.280 | 8.5.2 Requirements
| [R-8.5.2-001] For on network communications, priority management shall manage all data flows from the different mission critical services together when applying priority decisions.
NOTE 1: No mission critical service is considered as always having priority over another.
[R-8.5.2-002] For off network communications,... |
38055db1edaa9b8bf534dbc753cc4ba8 | 22.280 | 9.1 Service Description
| Mission critical users use aircrafts and helicopters for operational purpose. Being able to communicate in real time with helicopters and aircraft is a basic need.
Some traffic assumptions are provided in Annex D.
|
38055db1edaa9b8bf534dbc753cc4ba8 | 22.280 | 9.2 Requirements
| R-9.2-001 The MCX Service shall support Air ground air Communication up to 15.000 ft with a speed up to 450km/h.
|
38055db1edaa9b8bf534dbc753cc4ba8 | 22.280 | 10 MCX Service in IOPS mode
| [R-10-001] An MCX Service shall be able to provide services when operating in a 3GPP network in IOPS mode.
NOTE: Services may be reduced for example due to lack of back haul.
Annex A (normative):
MCCoRe Requirements for MCPTT
Table A.1 provides an exhaustive list of those requirements in 3GPP TS 22.280 that are a... |
2bcc1d4831fb70dd3621a5053d7410ff | 22.369 | 1 presented to TSG for information; | 2 presented to TSG for approval;
3 or greater indicates TSG approved document under change control.
y the second digit is incremented for all changes of substance, i.e. technical enhancements, corrections, updates, etc.
z the third digit is incremented when editorial only changes have been incorporated in the document.... |
2bcc1d4831fb70dd3621a5053d7410ff | 22.369 | 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.
- Fo... |
2bcc1d4831fb70dd3621a5053d7410ff | 22.369 | 3 Definitions of terms, symbols and abbreviations | |
2bcc1d4831fb70dd3621a5053d7410ff | 22.369 | 3.1 Terms | For the purposes of the present document, the terms given in 3GPP 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 3GPP TR 21.905 [1].
Ambient IoT device: As defined in TS 22.261 [4]. |
2bcc1d4831fb70dd3621a5053d7410ff | 22.369 | 3.2 (void) | |
2bcc1d4831fb70dd3621a5053d7410ff | 22.369 | 3.3 Abbreviations | For the purposes of the present document, the abbreviations given in 3GPP 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 3GPP TR 21.905 [1].
eMTC enhanced Machine-Type Communication
NB-IoT NarrowBand Intern... |
2bcc1d4831fb70dd3621a5053d7410ff | 22.369 | 4 Overview |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.