hash
stringlengths 32
32
| doc_id
stringlengths 5
12
| section
stringlengths 5
1.47k
| content
stringlengths 0
6.67M
|
|---|---|---|---|
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 configure IDs and aliases.
[R-6.9-004] The MCX Service shall provide the MCX Service User ID and /or associated aliases, the identity of the Selected MCX Service Group, and, if available, the identity of the Mission Critical Organization name of the transmitting MCX User to all MCX UEs that are receiving for display by each MCX UE.
|
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 Service Administrator designates that new or updated MCX Service User Profiles are to be installed at the MCX UE for immediate use by the MCX User.
[R-6.10-003] The MCX Service shall provide a means by which an MCX Service Administrator designates a particular time and date when new or updated MCX Service User Profiles are to be installed at the MCX UE for use by the MCX User.
[R-6.10-004] The MCX Service User Profile shall be construed to be sensitive user information and shall be provided end-to-end confidentiality and integrity protection when transferred between the MCX Service and MCX UE.
|
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 authorized MCX User to remotely log off another MCX User from an MCX UE.
|
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 authorized MCX User to restrict the dissemination of his Location information.
[R-6.12-004] The MCX Service shall provide end-to-end confidentiality of Location information.
[R-6.12-005] The MCX Service shall provide authentication of messages carrying Location information.
[R-6.12-006] The MCX Service shall provide a means for an authorized MCX User to activate a one-time Location information report of an MCX User and periodic Location information update reports of an MCX User or a specific Functional Alias.
[R-6.12-007] The MCX Service shall provide a means for an authorized MCX User to deactivate periodic Location information update report of an MCX User.
|
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 methods, or requiring upgrade of all user equipment simultaneously.
[R-6.13.2-003] The MCX Service shall allow for the coexistence of a multiplicity of cryptographic suites.
NOTE 1: A "cryptographic suite" is a consistent collection of cryptographic operations (e.g., encryption and message authentication) spanning the totality of required cryptographic operations for MCX Service. That is, if MCX Service requires a stream cipher, a message authentication code, and a secure hash, then counter-mode AES-256, CMAC with AES-256 as an underlying cipher, and SHA-512 would constitute a cryptographic suite for MCX Service.
NOTE 2: The definition and identification of cryptographic suites and algorithms need not all be within the scope of 3GPP.
|
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 Service shall provide a mechanism to temporarily disable an MCX UE remotely by the MCX Service Administrator or an authorized MCX User.
[R-6.13.4-004] The MCX Service shall only allow a user to affiliate to or select an enabled MCX Service Group (i.e., not disabled).
[R-6.13.4-005] A temporarily disabled MCX UE, which has limited access capability per Mission Critical Organization policy, shall be able to be re-enabled by the MCX Service Administrator or an authorized MCX User.
[R-6.13.4-006] The MCX Service shall provide a mechanism to re-enable a temporarily disabled MCX UE by the MCX Service Administrator or an authorized MCX User.
[R-6.13.4-007] The MCX Service shall provide a mechanism to permanently disable an MCX UE by the MCX Service Administrator or an authorized MCX User.
[R-6.13.4-008] The permanently disabled MCX UE shall remove all MCX Service User Profiles stored in the MCX UE.
[R-6.13.4-009] The permanently disabled MCX UE shall have no access to MCX Services.
[R-6.13.4-010] The security solution for the MCX Service shall minimize the impact of a compromised MCX UE on other MCX UEs.
|
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 and transmitting in one MCX Private Communication (without Floor control) while simultaneously receiving transmissions from other MCX Private Communications (with Floor control) within the same MCX service.
|
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 authorized MCX User to receive media and metadata of MCX Service Private Communication transmissions sent to and from a specific target MCX User that is within the authority of the authorized MCX User.
[R-6.15.1-002] The MCX Service shall provide a mechanism for an authorized MCX User to receive media and metadata of MCX Service Group Communication transmissions sent to and from a specific target MCX User that is within the authority of the authorized MCX User.
[R-6.15.1-002a] The MCX Service shall provide a mechanism for an authorized MCX User to receive media and metadata of MCX Service Ad hoc Group Communication transmissions sent to and from a specific target MCX User that is within the authority of the authorized MCX User.
[R-6.15.1-003] Subject to regulatory constraints and operator security policies, the MCX Service shall allow to be configured not to provide media and metadata of transmissions from MCX Users who are communicating with the discreet listening target MCX User, and who are not themselves targets of discreet listening.
[R-6.15.1-004] The MCX Service shall provide a mechanism for an authorized MCX User to receive media and metadata of MCX Service Group transmissions sent from a specific MCX Service Group that is within the authority of the authorized MCX User.
[R-6.15.1-005] The Discreet listening capabilities of the MCX service shall provide recording and playback capabilities to allow analysis and processing of media and metadata of the transmissions sent to and from a specific target MCX User that is within the authority of the authorized MCX User.
[R-6.15.1-006] The Discreet listening capabilities of the MCX service shall provide media and metadata of the transmissions sent to and from all the MCX devices that the specific target MCX User is logged into, where the metadata shall contain information about which of these MCX devices is involved in each of these transmissions.
NOTE: Permission to activate discreet listening can include multiple levels of authorization, but this is outside the scope of 3GPP.
|
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 to be "listened" to by another remote authorized MCX User or can be initiated by a remote authorized MCX User who wants to "listen" to another MCX User. The purpose of this feature allows a dispatcher to "listen" to activities at the Location of the remote MCX UE to find out what is happening around that MCX UE without providing an indication to the MCX User or people around the user (whom the MCX User does not want to make aware of this action) that this is happening. This type of communication is different from other types of communications, as for ambient listening information is only transmitted to one party in the communication (i.e., a dispatcher or an authorized MCX User that is acting in a similar role to a dispatcher).
This is used for stolen MCX UEs, monitoring officers, officer safety and particular operations, where it is important that the MCX UE does not indicate what is happening.
|
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 being listened to it shall appear to be turned off even while Ambient Listening continues to be active.
|
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 authorized MCX User (e.g., a dispatcher).
|
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 can be terminated by the MCX User being listened to or by the remote MCX Service Administrator and/or authorized user, who was the listening Participant.
|
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 activities at the Location of the remote MCX UE to find out what is happening around that MCX UE. This feature is also known as "Remote Unit Monitoring" in P25 systems.
There are two typical use cases for this feature.
The first one is the case where a user could have been incapacitated. This could be both accidentally, say a traffic accident, or deliberately, for example a violent attack. In both cases it would be necessary to remotely initiate a communication from the MCX UE in order to allow another user or a group of users to "listen" to what is happening to prepare assistance. The communication that is set up is either a Private Communication or a Group Communication, and the communication could optionally be visible to the remote MCX UE's user.
The second one is the case of a stolen MCX UE. Here it is just necessary to activate the MCX UE so that a dispatcher can "listen" to any background communication in order to make an analysis of the situation. In this situation, the initiation of the communication from the remote MCX UE, typically a Private Communication in that case, is not visible by that MCX UE's user.
Other use cases, such as undercover operations, discreet surveillance of users or investigations, could exist depending on the missions of the critical communications users and on legislations.
The behaviour of the remotely initiated Communication is not different from a normal communication initiated by the local MCX User. The same rules for resource allocation and interactions with other services apply, but the initiator of the feature can have the capability to request a pre-emptive or high priority for that Communication to ensure it is set up even in case of resource congestion or to limit disturbance by other services.
|
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 Administrator or authorized MCX User.
[R-6.15.3.2-002] The MCX Service shall provide a mechanism for an MCX Service Administrator and/or authorized user to provide a notification to the user of the MCX UE when a remote MCX Private Communication is initiated.
[R-6.15.3.2-003] The MCX Service shall provide a mechanism for an MCX Service Administrator and/or authorized user to cause an MCX UE that is within their authority to initiate an MCX Service Group Communication and then to begin transmitting to the Affiliated MCX Service Group Members.
[R-6.15.3.2-004] The MCX Service shall provide a mechanism for an MCX Service Administrator and/or authorized user to provide a notification to the user of the MCX UE when a remote MCX Service Group Communication is initiated.
|
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 receiving Participant(s).
[R-6.15.4-003] The MCX Service shall provide a mechanism for a Mission Critical Organization to record the transmissions of the Group Communications and Private Communications under the organization's authority.
[R-6.15.4-004] The MCX Service shall provide a mechanism for a Mission Critical Organization to log at least the following metadata per communication: depending on service this may include; start time, date, MCX User ID, functional alias(es), MCX Group ID, Location information of the transmitting Participant, end time or duration, end reason, type of communication (e.g., MCX Service Emergency, regroup, private) and success/failure indication.
[R-6.15.4-005] If an MCX Service Group Communication or MCX Service Private Communication uses end-to-end confidentiality, the MCX Service shall provide a mechanism for a Mission Critical Organization to maintain the end-to-end confidentiality when the MCX Service Group Communication or MCX Service Private Communication is logged.
[R-6.15.4-006] The MCX Service shall provide a mechanism for a Mission Critical Organization to log the metadata of non-communication related user activities under the agency's authority.
[R-6.15.4-007] The MCX Service shall provide a mechanism for a Mission Critical Organization to log at least the following non-communication activity types: MCX Service Emergency Alert, MCX Service Emergency Alert cancellation, In-progress Emergency cancellation, registration state change, overridden event, user remote logout, changing another user's affiliations, affiliation change, change of Selected MCX Service Group, (de)activation of functional alias(es) and User and Group Regroup operations.
[R-6.15.4-008] The MCX Service shall provide a mechanism for a Mission Critical Organization to log at least the following metadata per non-communication activity: time, date, MCX Service User identity, activity type and pertinent information about the activity (e.g. MCX User/Group ID(s) included in the temporary group created by the User/Group Regroup operation). The following metadata should be logged if applicable to the activity type: MCX Service Group ID, Location information of the MCX User, affiliation list, target MCX Service User ID and success/failure indication.
[R-6.15.4-009] The MCX Service shall provide a mechanism for a Mission Critical Organization to log metadata for all failed authorization attempts (e.g., invalid login password) by an MCX User.
[R-6.15.4-010] The MCX Service shall provide a mechanism to collect metadata for network access events (e.g., pre-emption of the 3GPP system bearer services, loss of signal, failed registration attempts).
[R-6.15.4-011] The MCX Service shall provide recording and audit functions for all types of MCX Service group communication (e.g., normal group, regroup group, Ad hoc group).
|
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 group communication. The main characteristics of this ad hoc group communication are:
a) The ad hoc group does not exist until it is spontaneously created during the communication.
b) The ad hoc group ceases to exist when the communication terminates.
A single communication consists of one or more media transmissions until explicitly terminated by various means. MCX Users that are being combined in an ad hoc group communication may be served by the same or different MCX systems and may normally use MCX Service Groups with different security and priority levels, different floor control methods, and other different operational characteristics. The MCX Service Ad hoc Group Communication will use a common security level, priority level, floor control method, and set of operational characteristics for the participants during a communication. As with any group communication, the priority level can change dynamically.
The ad hoc group is used for a single communication and it does not persist when the communication is terminated. Authorized users can recreate the ad hoc group for subsequent communications, or request creation of a permanent MCX Service Group from the participants in the ad hoc group communication.
NOTE: When the MCX Service Ad hoc Communication is terminated the list of participants may be retained for ease of initiating another ad hoc communication with the same participants.
|
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 of MCX Users can be manual, or automatic based on certain criteria (e.g., location). This is left for implementation.
[R-6.15.5.2-001a] The MCX Service shall provide the reason for denial to an MCX user who was not authorised to initiate an MCX Service Ad hoc Group Communication.
[R-6.15.5.2-001b] The participant of an MCX Ad hoc Group Communication who has activated several Functional Alias(es) shall receive only one communication based on the unique MCX Service ID.
[R-6.15.5.2-001c] The MCX Service shall provide a mechanism for the participant of an Ad hoc Group Communication to determine the Functional Alias, through which this participant is addressed by the communication.
[R-6.15.5.2-001d] The MCX Service shall enable the receiving participant of an Ad hoc Group Communication to respond including the Functional Alias
[R-6.15.5.2-002] An MCX Service Ad hoc Group Communication is a type of MCX Service Group communication and shall support MCX Service Group Communication mechanisms for call processing (e.g., transmit request queuing, hang time, broadcast mode).
[R-6.15.5.2-003] MCX Service Ad hoc Group Communications shall be terminated by an authorised user or using the same mechanisms as MCX Service Group communications (e.g., initiator release, server release, hang time expiration).
[R-6.15.5.2-004] The MCX Service shall provide a mechanism for an MCX Service Administrator to configure additional conditions under which MCX Service Ad hoc Group Communication shall be terminated (e.g., last Participant leaving, second last Participant leaving, initiator leaving).
[R-6.15.5.2-005] When an MCX Service Ad hoc Group Communication is terminated the group shall not persist.
[R-6.15.5.2-006] The MCX Service shall provide a mechanism for the initiator of a MCX Service Ad hoc Group Communication to indicate which MCX Users have to mandatorily acknowledge the setup request before the media transmission proceeds.
[R-6.15.5.2-007] The MCX Service shall provide a mechanism for an authorized initiator of a MCX Service Ad hoc Group Communication to define the communication parameters for the Ad hoc Group Communication (e.g. priority, hang time, broadcast/non-broadcast)
[R-6.15.5.2-008] MCX Service Ad hoc Group Communications shall be able to support the same urgency as MCX Service Group communication (e.g., general group, emergency, imminent peril).
[R-6.15.5.2-009] MCX Service Ad hoc Group Communications shall support the applicable security requirements as identified in sub-clause 5.12.
[R-6.15.5.2-010] The MCX Service shall provide a mechanism for the initiator of an MCX Service Ad hoc Group Communication to request that the list of participants is suppressed.
[R-6.15.5.2-011] The MCX Service shall provide a mechanism for authorized MCX Users to create a permanent MCX Service Group from the members of the MCX Service Ad hoc Group communication.
[R-6.15.5.2-012] The MCX Service shall provide a mechanism for the initiator and/or an authorised user to add or remove participants during an in progress MCX Service Ad hoc Group communication.
[R-6.15.5.2-013] The MCX Service shall provide a mechanism for a participant to join an in progress MCX Service Ad hoc Group communication.
[R-6.15.5.2-014] The MCX Service shall provide a mechanism for the initiator of an MCX Service Ad hoc Group Communication to request that the list of participants with their corresponding Functional Aliases, be determined and updated by the MCX Service system using pre-defined criteria.
[R-6.15.5.2-014a] When the list of participants is determined or updated by the MCX Service system, the MCX Service shall provide a mechanism that monitors and ensures that the participants list is applied for an MCX Service Ad hoc Group communication, performing retries when needed.
[R-6.15.5.2-015] The MCX Service shall provide a mechanism for a participant of an MCX Service Ad hoc Group Communication to provide his location information to an authorised participant of the same group.
[R-6.15.5.2-016] The MCX Service shall provide a mechanism for an authorized MCX User to combine multiple Ad hoc Group communications.
[R-6.15.5.2-017] The MCX Service shall provide notifications to the relevant participants and authorized users of the combined Ad hoc Group communication.
[R-6.15.5.2-018] The MCX Service shall provide to the participants of the combined Ad hoc Group communication, the same MCX User authorizations for modifying or terminating a call, as in the previous original Ad hoc Group communications.
|
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 Administrator to configure the maximum number of MCX Users who can participate in a MCX Service Ad hoc Group Communication.
[R-6.15.5.3-003] The MCX Service shall provide a mechanism for an MCX Service Administrator to configure which MCX Users are authorized to participate in a MCX Service Ad hoc Group Communication.
[R-6.15.5.3-004] The MCX Service shall provide a mechanism for an MCX Service Administrator to define the default parameters for MCX Service Ad hoc Group communication (e.g., priority, hang time, broadcast mode).
[R-6.15.5.3-005] The MCX Service shall provide a mechanism for an MCX Service Administrator to configure whether MCX Service Ad hoc Group Communication is allowed on the MCX system regardless of individual MCX User authorizations.
[R-6.15.5.3-006] The MCX Service shall provide a mechanism for an MCX Service Administrator to configure which MCX Usersare authorized to combine Ad hoc Group Communications.
|
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 MCX Service Ad hoc Group Communications a participant is considered an affiliated member of the group during communication setup.
[R-6.15.5.4-002] The MCX Service shall provide notifications to authorized users, including, if available, the corresponding Functional Aliases of the determined or updated list of participants.
|
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 Users based on criteria into a group and to send an emergency alert to this set of MCX Users.
The main characteristics of the Ad hoc Group Emergency Alert are:
a) The ad hoc group does not exist until it is spontaneously created at the initiation of the Ad hoc Group Emergency Alert.
b) After initiation of the Ad hoc Group Emergency Alert the MCX User may be put into the MCX Service Emergency State.
c) After initiation of the Ad hoc Group Emergency Alert the resulting ad hoc group may be used for group communications.
d) The ad hoc group ceases to exist when the group communications in the ad hoc group have terminated, and the Ad hoc Group Emergency Alert has been cancelled.
An authorised user is able to:
a) Initiate an MCX Service Ad hoc Group Emergency Alert with participants satisfying specific criteria,
b) Cancel an MCX Service Ad hoc Group Emergency Alert,
During an ongoing MCX Service Ad hoc Group Emergency Alert, the set of MCX Users may change dynamically based on these criteria (e.g., criteria may not longer be met, or criteria may be met for additional MCX users, and as a result users are removed from or added to the ongoing Ad hoc Group Emergency Alert).
|
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-006
6.15.6.4 Notification and acknowledgement for MCX Service Ad hoc Group Emergency Alert
R-6.15.6.4-001
R-6.15.6.4-002
6.16 Interaction with telephony services
R-6.16-001
R-6.16-002
6.17 Interworking
NA
6.17.1 Non-3GPP access
R-6.17.1-001
6.17.2 Interworking between MCX Service systems
R-6.17.2-001
R-6.17.2-002
R-6.17.2-003
R-6.17.2-004
R-6.17.2-005
R-6.17.2-006
R-6.17.2-007
R-6.17.2-008
6.17.3 Interworking with non-MCX Service systems
NA
6.17.3.1 GSM-R
R-6.17.3.1-001
R-6.17.3.1-002
R-6.17.3.1-003
R-6.17.3.1-004
R-6.17.3.1-005
6.17.3.2 External systems
R.6.17.3.2-001
R.6.17.3.2-002
6.18 MCX Service coverage extension using ProSe UE-to-Network Relays
R-6.18-001
R-6.18-002
R-6.18-003
R-6.18-004
R-6.18-005
R-6.18-006
6.19 Additional MCX Service requirements
NA
6.19.1 Communication rejection and queuing
NA
6.19.1.1 Requirements
R-6.19.1.1-001
R-6.19.1.1-002
R-6.19.1.1-003
R-6.19.1.1-004
R-6.19.1.1-005
R-6.19.1.1-006
R-6.19.1.1-007
7 MCX Service requirements specific to off-network use
NA
7.1 Off-network communications overview
NA
7.2 General off-network MCX Service requirements
R-7.2-001
R-7.2-002
R-7.2-003
R-7.2-004
R-7.2-005
7.3 Admission control
NA
7.3.1 General aspects
R-7.3.1-001
R-7.3.1-002
R-7.3.1-003
7.3.2 Communication initiation
R-7.3.2-001
R-7.3.2-002
R-7.3.2-003
R-7.3.2-004
R-7.3.2-005
7.4 Communication termination
R-7.4-001
R-7.4-002
R-7.4-003
R-7.4-004
7.5 Broadcast Group
R-7.5-001
R-7.5-002
7.6 MCX Service priority requirements
R-7.6-001
R-7.6-002
R-7.6-003
R-7.6-004
R-7.6-005
R-7.6-006
R-7.6-007
R-7.6-008
R-7.6-009
7.7 Communication types based on priorities
NA
7.7.1 MCX Service Emergency Group Communication requirements
R-7.7.1-001
R-7.7.1-002
R-7.7.1-003
7.7.2 MCX Service Emergency Group Communication cancellation requirements
R-7.7.2-001
7.7.3 Imminent Peril Communication
NA
7.7.3.1 Imminent Peril Group Communication requirements
R-7.7.3.1-001
R-7.7.3.1-002
R-7.7.3.1-003
R-7.7.3.1-004
R-7.7.3.1-005
7.7.3.2 Imminent Peril Group Communication cancellation requirements
R-7.7.3.2-001
R-7.7.3.2-002
7.8 Location
R-7.8-001
R-7.8-002
R-7.8-003
7.9 Security
R-7.9-001
R-7.9-002
7.10 Off-network MCX Service operations
R-7.10-001
R-7.10-002
R-7.10-003
7.11 Off-network UE functionality
R-7.11-001
R-7.11-002
R-7.11-003
7.12 Streaming for ProSe UE-to-UE Relay and UE-to-Network Relay
NA
7.12.1 UE-to-Network Relay for all data types
R-7.12.1-001
R-7.12.1-002
R-7.12.1-003
R-7.12.1-004
7.12.2 UE-to-UE Relay streaming
R-7.12.2-001
R-7.12.2-002
R-7.12.2-003
7.12.3 Off-Network streaming
R-7.12.3-001
R-7.12.3-002
R-7.12.3-003
7.13 Switching to off-network MCX Service
R-7.13-001
R-7.13-002
R-7.13-003
R-7.13-004
R-7.13-005
7.14 Off-network recording and audit requirements
R-7.14-001
R-7.14-001a
R-7.14-002
R-7.14-002a
7.15 Off-network UE-to-UE relay
NA
7.15.1 Private Communications
R-7.15.1-001
R-7.15.1-002
R-7.15.1-003
7.15.2 Group Communications
R-7.15.2-001
R-7.15.2-002
|
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 configure the maximum number of MCX Users who can participate in a MCX Service Ad hoc Group Emergency Alert.
[R-6.15.6.3-003] The MCX Service shall provide a mechanism for an MCX Service Administrator to configure which MCX Users are authorized to participate in a MCX Service Ad hoc Group Emergency Alert.
[R-6.15.6.3-004] The MCX Service shall provide a mechanism for an MCX Service Administrator to define the default parameters for the ad hoc group resulting from the MCX Service Ad hoc Group Emergency Alert (e.g., priority, hang time, broadcast mode).
[R-6.15.6.3-005] The MCX Service shall provide a mechanism for an MCX Service Administrator to configure whether MCX Service Ad hoc Group Emergency Alert is allowed on the MCX system regardless of individual MCX User authorizations.
[R-6.15.6.3-006] The MCX Service shall provide a mechanism for an MCX Service Administrator to configure which MCX Users, within their authority, are authorized to combine Ad hoc Group Emergency Alerts.
|
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 authorized users, including, if available, the Functional aliases of the receiving participants.
|
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 telephony services to block incoming telephony calls.
|
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 System shall be based on security parameters obtained from the Primary MCX Service System of the MCX User.
NOTE 1: This is an application layer authentication and not 3GPP network authentication.
[R-6.17.2-003] Any functionality needed from the visited PLMN network is subject to roaming capabilities and operator agreement.
[R-6.17.2-004] An MCX Service shall provide mechanisms to allow an MCX User on the Primary MCX Service System to affiliate and communicate in an MCX Service Group from a Partner MCX Service System, subject to authorization from the Primary MCX Service System and the Partner MCX Service System where the MCX Service Group is defined.
[R-6.17.2-005] An MCX Service shall provide mechanisms to allow a roaming MCX User to affiliate and communicate in an MCX Service Group from the Partner MCX Service System, subject to authorization from the Partner MCX Service System where the MCX Service Group is defined.
[R-6.17.2-006] An MCX Service shall provide mechanisms to allow an MCX User that receives service from a Partner MCX Service System to affiliate and communicate in an MCX Service Group from another Partner MCX Service System, subject to authorization from the Partner MCX Service System where the MCX Service Group is defined.
[R-6.17.2-007] End to end security of an MCX Service Group communication (including in Partner MCX Service Systems) shall be based on parameters obtained from the MCX Service system where the MCX Service Group is defined.
[R-6.17.2-008] The MCX Service shall enable to establish an MCX Service Ad hoc Group Emergency Alert and MCX Ad hoc Group Communication with Participants of multiple MC Systems, which are interconnected.
|
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) standards [9] and EN 301 515 [10].
NOTE: The impact on GSM-R needs to be minimised.
[R-6.17.3.1-003] The MCX Service system shall enable interworking between functional alias and alternative addressing scheme used in GSM-R.
[R-6.17.3.1-004] A GSM-R user shall be reachable using the corresponding functional alias activated by the MCX Service system.
[R-6.17.3.1-005] The MCX Service shall allow an MCX User to be reachable by a functional alias on the MCX Service system or on the GSM-R system.
|
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 with PLMN and PSTN telephony services.
|
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 relay shall advertise, at the ProSe interface, those MCX Services (Groups) which it is currently relaying.
[R-6.18-003] An MCX UE which is unable to gain service from a 3GPP network shall search for ProSe UE-to-Network Relay(s) offering MCX Services for the affiliated MCX Service Groups of the MCX User.
[R-6.18-004] A ProSe UE-to-Network Relay authorized to support MCX Service coverage extension relay between an MCX UE and the on-network MCX Service shall provide a mechanism for an off-network MCX UE to affiliate to one or more MCX Service Groups using the on-network MCX Service.
[R-6.18-005] The ProSe UE-to-Network Relay that has enabled an MCX UE to affiliate to an MCX Service Group using the on-network MCX Service shall subsequently support the bi-directional relay of signalling (control plane) and data (user plane) between the MCX UE and the on-network MCX Service for that MCX Service Group.
[R-6.18-006] A ProSe UE-to-Network Relay authorized to support the bi-directional relay of signalling (control plane) and data (user plane) between an MCX UE and the on-network MCX Service shall provide a mechanism for an off-network MCX UE to initiate and/or receive Private Communications using the on-network MCX Service.
|
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 immediately granted, rejected, or queued. If queued, a request to transmit is normally granted when conditions which caused the queue are removed, or it can be dropped automatically for a number of reasons, or it can be cancelled by an authorized user who is usually the initiator of the request to transmit. When a request to transmit is rejected, it can be re-requested either manually by user action or automatically.
|
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 more authorized users when a communication is queued, when a communication is rejected, when communications has started after being de-queued.
[R-6.19.1.1-004] The MCX Service shall provide a mechanism for an MCX User to remove its MCX request to transmit from the MCX request queue.
[R-6.19.1.1-005] The MCX Service shall provide a mechanism for an authorised user to remove another user’s MCX request to transmit from the MCX request queue.
[R-6.19.1.1-005a] The MCX Service shall provide a mechanism for an authorised user to clear the entire MCX request queue.
[R-6.19.1.1-006] An MCX Service User shall be notified when his request to transmit is removed from the MCX request queue.
[R-6.19.1.1-007] The MCX Service shall provide a mechanism for an MCX Administrator to configure service parameter(s) (e.g., timer) for automatic removal of an MCX request to transmit from any MCX request queue.
|
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 not traverse the network infrastructure.
Users operating off the network are either out of network coverage (not served by a 3GPP network) (e.g., in a remote mountain area fighting a forest fire 20 miles from the nearest network) or have selected a ProSe direct communication path for MCX Service while in network coverage. MCX Users operating off the network need to be in ProSe direct communication range in order to communicate.
NOTE 1: While the network is likely to be a primary, reliable transport of MCX Service communications, there are many situations where MCX Service communications are needed in areas where the network is not available, or coverage is not reliable.
MCX Users outside of the coverage of the fixed network might be first responders in a rural area assisting in a response to a plane crash, fire fighters in a remote mountain area fighting a forest fire or police officers inside a residence responding to a domestic issue. Off-network MCX Service communications are expected to be immediately accessible to users in the absence of the network.
MCX Users in network coverage might be working in a confined area, such as fire fighters fighting a structure fire where direct UE-to-UE communication is more desirable and reliable. Users can communicate directly with one another without having to overcome the resistance of a building and distance to the nearest base station to communicate with other members of their team inside the building that are nearby.
To operate off the network, an MCX UE is capable of automatically switching to a ProSe direct communication path for use of MCX Services when detecting an off-network (out of coverage) condition. In addition, a mechanism is provided for an authorized user to select (manually switch to) a ProSe direct communication path for use of off-network MCX Service communications (e.g., while in network coverage).
When operating off the network, the MCX Service is provided by the MCX Service Application on the UE as compared to operations on the network, where the MCX Service Application on the UE interacts with an MCX Service server and the network to provide the MCX Service.
NOTE 2: For MCX UEs that have selected a ProSe Direct Communication path for use of MCX Services while in network coverage, signalling with the network and MCX Service might be available (e.g., radio resource allocation, MCX Service User Profile management updates and cryptographic key management updates), while the MCX User transmissions would be direct between the MCX UEs (e.g., not traversing the network).
The Off-Network MCX Service builds upon ProSe enablers to establish, maintain and terminate the signalling and communication path(s) among the off-network users. To the extent feasible, it is expected that the end user's experience is similar regardless if the MCX Service is used with a 3GPP network or based on the use of a ProSe direct communication path.
The Off-Network MCX Service is intended to support communication between a group of users (a group communication), where each user has the ability to gain access to transmit in an arbitrated manner. However, the MCX Service also supports Private Communications between pairs of users.
When operating off the network the MCX Service allows users to request the permission to transmit (transmit voice/audio) and provides a deterministic mechanism to arbitrate between requests that are in contention (i.e., Floor control).
The Off-Network MCX Service provides a means for a user with higher priority (e.g., MCX Service Emergency condition) to override (interrupt) the current sender. The Off-Network MCX Service also supports a mechanism to limit the time a user transmits (has access to the resources) thus permitting users of the same or lower priority a chance to gain access to the resources.
The Off-Network MCX Service provides the means for a user to monitor activity on a number of separate communications and enables the user to switch focus to a chosen communication. An Off-Network MCX User might join an already established MCX Service Group Communication (Late communication entry). In addition the Off-Network MCX Service supports MCX Service User IDs, aliases and user Location determination features.
For operation off the network (e.g., when out of network coverage), an MCX UE is (pre-)provisioned by an MCX Service Administrator and/or authorized user with the following in order to use MCX Services:
a) An MCX Service User Profile associated with each of the intended MCX Users of the MCX UE that might be used for off-network operation;
1) An alphanumeric identifier (with a minimum length of Nc3) (i.e., alias) for each MCX User;
2) A number of off-network MCX Service Groups for use by the MCX User;
3) An alphanumeric identifier (i.e., alias) for the authorized off-network MCX Service Groups;
4) A Mission Critical Organization name if available, associated with each of the intended MCX Users or Administrator;
5) A number of off-network MCX Users for Private Communications for which the MCX User is authorized;
b) Authentication and end-to-end security keys.
NOTE 3: MCX UEs can be provisioned for off-network use by either configuration outside of network coverage or by attaching to the network.
An MCX UE operating off the network is capable of transmitting the sender’s Location information, MCX Service User ID, alias(es), off-network MCX Service Group ID, group alias and, if available, Mission Critical Organization name of the user who is transmitting (i.e., whose UE is transmitting) to all other users in a communication including MCX UEs operating off the network that are late entering a communication in progress.
The Off-Network MCX Service uses the capabilities defined in ProSe TS 22.278 [5], including the ProSe Relay capabilities defined in ProSe TS 22.278 [5] and GCSE_LTE TS 22.468 [6].
NOTE 4: As indicated in TS 22.278 [5] use of a ProSe Direct Communication path outside of network coverage is only applicable for Public Safety ProSe enabled UEs. For non-Public Safety ProSe enabled UEs the selection of the most appropriate communication path (ProSe Communication path (direct or routed via local basestation) or 3GPP network path) is under network control and based on operator preferences.
MCX Service requirements specific to off-network use are defined in clause 7. Common MCX Service requirements defined in clause 5 apply whether the MCX Service is in use on the network or off the network.
|
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-enabled UEs as defined in TS 22.278 [5].
[R-7.2-003] The MCX Service shall provide a mechanism for an MCX Service Administrator and/or authorized user to pre-provision MCX UEs that may not be served by the network with the following in order to operate using off-network MCX Service:
a) An MCX Service User Profile associated with each of the intended MCX Users of the MCX UE that might be used for off-network operation:
1) alphanumeric identifier (i.e., Alias ID) for the authorized off-network MCX Service Groups;
2) a number of off-network MCX Service Groups for use by an MCX User;
3) a MCX Service User ID associated with each of the intended MCX Users;
4) an alphanumeric identifier (with a minimum length of Nc3) (i.e., alias) for each MCX Service User ID.
b) authentication and end to end security keys.
NOTE: MCX UEs can be provisioned for off-network use by either configuration outside of network coverage or by attaching to the network.
[R-7.2-004] An MCX UE operating off the network shall be capable of transmitting the MCX Service User ID, alias(es), off-network MCX Service Group and, if available, Mission Critical Organization name of the user who is talking (i.e., whose UE is transmitting) to all other users in the communication including MCX UEs operating off the network that enter the communication late.
[R-7.2-005] An MCX UE operating off the network shall be capable of transmitting the sender's Location information (i.e., whose UE is transmitting) to all other users in the communication including MCX UEs operating off the network that enter the communication late.
|
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 shall take into account priorities of all MCX Services communications as well as the resources they take/need.
[R-7.3.1-003] The off-network Floor control functionality in an MCX Service shall determine at a point in time which received transmission(s) from off-network Participant(s) shall be presented to the receiving off-network Participant(s).
7.3.2 Communication initiation
[R-7.3.2-001] An authorized participant shall be able to request to start a communication.
[R-7.3.2-002] The admission control functionality shall determine if an MCX User is allowed to start a communication and transmit according to resource management.
[R-7.3.2-003] Following an off network MCX Service request for permission to transmit on the Selected MCX Group, the Affiliated MCX Group Member that made and was granted the request shall be given an indication of being granted permission to transmit.
[R-7.3.2-004] When an MCX User is not allowed to start a communication, the MCX Service shall notify the MCX User that his communication has been queued or rejected.
[R-7.3.2-005] When an MCX User is not allowed to start a communication the request may be queued or rejected.
|
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 network shall provide an indication to the Participants that the communication is within a configurable amount of time before the communication time limit is reached.
[R-7.4-003] The MCX Service when operating off the network shall provide an indication to the Participants that the communication time limit has been reached.
[R-7.4-004] The MCX Service when operating off the network shall release the communication when the communication time limit has been reached.
|
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 may be all of the MCX Service system users, or a subset thereof.
|
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 priority.
[R-7.6-003] The Off-Network MCX Service shall support multiple MCX Service Application priorities which are mapped to ProSe priority levels, based on network operator policy.
[R-7.6-004] The Off-Network MCX Service shall enable an MCX Service Administrator to prioritize MCX Groups in relation to other MCX Groups (with respect to transport and presentation).
[R-7.6-005] When determining priority for an MCX communication, the Off-Network MCX Service shall use the MCX User/Participant's attributes (e.g., first/second responder, supervisor, dispatcher, on/off duty) and the MCX Group's attributes (e.g., type of group, owning organization of the group, MCX Emergency, Imminent Peril).
[R-7.6-006] The Off-Network MCX Service shall support multiple pre-emptive priorities.
[R-7.6-007] The Off-Network MCX Service shall provide a mechanism for MCX Administrators to create, a pre-emption hierarchy for MCX Group communications and their associated users (i.e., to facilitate local management of the service and its resources).
[R-7.6-008] The Off-Network MCX Service shall support MCX Groups with the permission to pre-empt other MCX communications.
[R-7.6-009] In case of resource shortage an MCX communication made to a group with pre-emption permissions shall be given resources to complete this communication by pre-empting lower priority MCX communications.
|
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-network MCX UE that has initiated the MCX Service Emergency Group Communication shall maintain knowledge of the in progress off-network MCX Service Emergency Group Communication until it is cancelled.
[R-7.7.1-003] An off-network MCX UE initiating an off-network MCX Service Emergency Group Communication shall be capable of transmitting its MCX Service User ID and an indication that it is an off-network MCX Service Emergency Group Communication to all other users in the communication.
|
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.3.1-002] If an MCX Service Group has previously been configured to be used for Imminent Peril communications by the MCX User, that MCX Service Group shall be used for the communication.
[R-7.7.3.1-003] The MCX Service when operating in off-network mode shall provide a mechanism, for an authorized Participant of an in progress off-network MCX Service Group Communication, to change the status of the communication to an off-network MCX Service Imminent Peril group communication.
[R-7.7.3.1-004] The off-network MCX UE that has initiated an MCX Service Imminent Peril group communication shall be responsible for maintaining the knowledge of the Imminent Peril status until it is cancelled.
[R-7.7.3.1-005] The Off-Network MCX Service shall provide a mechanism to inform and keep updated other Participants of the MCX Service Group Communication regarding the Imminent Peril status of the communication and regarding the MCX Service User ID of the MCX User setting the status to Imminent Peril.
7.7.3.2 Imminent Peril Group Communication cancellation requirements
[R-7.7.3.2-001] An indication of the cancellation of the Imminent Peril status of an off-network MCX Service Imminent Peril group communication and the MCX Service User ID of the cancelling user shall be transmitted to Affiliated MCX Service Group Members of an off-network MCX Service Imminent Peril group communication.
[R-7.7.3.2-002] If the Imminent Peril status of an MCX Service Imminent Peril group communication is cancelled by an MCX User other than the user initiating the Imminent Peril status, then the Off-Network MCX Service shall provide a mechanism to clear the knowledge of the Imminent Peril status maintained at the UE of the initiating MCX User.
|
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.
[R-7.8-003] The Off-Network MCX Service shall provide a means for an authorized MCX User to activate a one-time Location information report of a particular target MCX User 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-Network MCX Services.
|
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 groups, and concurrent communications on and off the network involving both groups and Private Communications. This concurrent communication is not defined as a ProSe relay.
[R-7.11-002] When switching from on-network to off-network operation (either manually or automatically), an MCX UE should attempt to notify the MCX Service that it is leaving the network.
[R-7.11-003] Prior to automatically going off the network an MCX UE should attempt to make use of suitable ProSe UE-to-Network Relay in its proximity.
|
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 MCX User to forward real-time data (e.g. voice, streaming video/data) from an MCX User to another MCX User across a ProSe UE-to-Network relay using the MCX UE-to-Network Relay service.
[R-7.12.1-003] The MCX Service shall provide a mechanism for an MCX Service Administrator to authorize an MCX User to forward real time data (e.g. voice, streaming video/data) from one MCX User to another MCX User.
[R-7.12.1-004] The MCX Service shall provide a mechanism to select/re-select a UE-to-Network Relay node that has enough capability for the real time data (e.g. video) forwarding.
|
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 when an MCX UE transitions its connection for that communication from on-network operation to off-network operation via a ProSe UE-to-UE relay.
[R-7.12.2-003] The MCX Service shall minimize the interruption to an on-going MCX Service communication when an MCX UE transitions its connection for that communication from off-network operation via a ProSe UE-to-UE relay to on-network operation.
|
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 for that communication from a ProSe UE-to-UE relay to ProSe direct communications with another MCX UE.
[R-7.12.3-003] The MCX Service shall minimize the interruption to an on-going MCX Service communication when an MCX UE transitions its connection for that communication from ProSe direct communications with another MCX UE to a ProSe UE-to-UE relay.
|
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 ProSe direct communication path for use of Off-Network MCX Service while in network coverage.
[R-7.13-003] Subject to operator policy and/or network authorization, a means shall be provided for an authorized MCX User using a Public Safety ProSe-enabled UE to be able to manually switch between the on-network operation and a ProSe direct communication path for use of Off-Network MCX Service while in network coverage or out of network coverage.
[R-7.13-004] An MCX Service shall minimize the interruption to an on-going MCX Service communication when an MCX UE transitions its connection to that communication from on-network operation to off-network ProSe direct communication with another MCX UE.
[R-7.13-005] An MCX Service shall minimize the interruption to an on-going MCX Service communication when an MCX UE transitions its connection to that communication from off-network ProSe direct communication with another MCX UE to on-network operation.
|
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-network mode. Metadata shall be logged for both the transmitting Participant and the receiving Participant(s).
[R-7.14-001a] The Off-Network MCX Service shall provide a mechanism for a Mission Critical Organization to record the media content of the transmitting Participant of Group Communications and Private Communications under the organization's authority from MCX UEs operating in off-network mode.
NOTE: The handling of storage limitation of the UE is out of scope of 3GPP.
[R-7.14-002] Upon return to on-network operation, the MCX Service shall provide a mechanism to retrieve communication and non-communication activity metadata from an MCX UE that has collected such metadata while operating in off-network mode.
[R-7.14-002a] Upon return to on-network operation, the MCX Service shall provide a mechanism to retrieve the media content of the transmitting Participant of Group Communications and Private Communications from an MCX UE that has recorded such media content while operating in off-network mode.
|
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 particular target MCX User is within ProSe direct communication range.
[R-7.15.1-003] An MCX UE shall be able to:
- discover whether the UE of the target MCX User is itself within direct communication range of the source UE; and if not;
- instead discover whether the UE of the target MCX User is within communication range of a ProSe UE-to-UE Relay that is within direct communication range of the source UE.
|
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 receiving both the original MCX Service Group transmission and a relayed transmission shall be able to associate the two transmissions, correctly order a mixture of packets (received directly and indirectly) and identify duplicate packets.
|
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 Requirements
R-8.2.2-001
R-8.2.2-002
R-8.2.2-003
R-8.2.2-004
R-8.2.2-005
R-8.2.2-006
R-8.2.2-007
8.3 Use of unsharable resources within a UE
R-8.3-001
R-8.3-002
R-8.3-003
R-8.3-004
R-8.3-005
R-8.3-006
8.4 Single Group with multiple MCX Services
NA
8.4.1 Overview
NA
8.4.2 Requirements
R-8.4.2-001
R-8.4.2-002
R-8.4.2-003
R-8.4.2-004
R-8.4.2-005
8.4.3 Compatibility of UE
NA
8.4.3.1 Advertising service capabilities required
R-8.4.3.1-001
R-8.4.3.1-002
R-8.4.3.1-003
R-8.4.3.1-004
8.4.3.2 Conversion between capabilities
R-8.4.3.2-001
8.4.4 Individual permissions for service access
R-8.4.4-001
8.4.5 Common alias and user identities or mappable
R-8.4.5-001
8.4.6 Single location message
R-8.4.6-001
R-8.4.6-002
R-8.4.6-003
8.5 Priority between services
NA
8.5.1 Overview
NA
8.5.2 Requirements
R-8.5.2-001
R-8.5.2-002
R-8.5.2-003
R-8.5.2-004
R-8.5.2-005
9 Air Ground Air Communications
NA
9.1 Service description
NA
9.2 Requirements
R-9.2-001
10 MCX Service in IOPS mode
R-10-001
Annex D (informative):
Characteristics and traffic assumptions for air ground air communications
The mission critical air ground air communications will be used as described below.
D.1 Environment
Helicopters are used for rescue and providing reconnaissance information to support events/incidents in rural (including mountains) environments and urban environments. Helicopters are also used for rescue and providing reconnaissance support for events/incidents in the ocean within a limited range of land or ship.
Planes are often used in rural (including forests and mountains) environment, but they can also be used in and near urban areas.
D.2 Altitudes
Helicopters have an altitude of 1.500 ft in general but in mountains it goes up to 15.000 ft.
Planes have an altitude between 2.000 ft and 15.000 ft.
The system will have to operate from 500 ft above ground level/above the sea with service continuity between ground communications and air ground air communications.
D.3 Maximum speed and mobility
Helicopters are moving at a speed of 250 km/h, planes are moving at 450 km/h. The ascent and descent speed are up to 1.000 ft per minute.
D.4 Traffic assumptions
For a region of 90.000 km2, a minimum of 18 communications per regions are supported with at least 6 simultaneous communications for helicopters and at least 6 simultaneous communications for planes.
Annex E (informative):
Variables
Table E.1: List of variables
Variable
Meaning
Reference
Bc1
Number of levels of group hierarchy within an MCX Service
5.2.2
Bc2
Number of levels of user hierarchy within an MCX Service
5.2.3
Nc1
Number of receiving members present for an MCX Group.
6.4.2
Nc2
Total number of MCX Groups that an MCX User can be affiliated to simultaneously
5.1.5
Nc3
Minimum length of alphanumeric identifiers (i.e., Alias ID)
5.7, 6.4.3, 7.1, and 7.2
Nc4
Number of simultaneous MCX Group communications received by an MCX UE
5.4.2
Nc5
Number of simultaneous MCX Group communications received by a user
5.4.2
Nc6
Total number of MCX Group Members of an MCX Group
6.1
Annex F (informative):
Change history
Change history
TSG SA#
SA Doc.
SA1 Doc
Spec
CR
Rev
Rel
Cat
Subject/Comment
Old
New
WI
SP-73
SP-160543
S1-162406
22.280
0001
1
Rel-14
F
Corrections to referenced sub-clauses in Annex B and Annex C
14.0.0
14.1.0
MCImp-MCCoRe
SP-73
SP-160543
S1-162407
22.280
0003
1
Rel-14
D
Add an Informative Annex table in MCCoRe TS 22.280 with a List of Variables used
14.0.0
14.1.0
MCImp-MCCoRe
SP-73
SP-160543
S1-162403
22.280
0004
1
Rel-14
F
Add definitions for participant and participant type to MCCoRe TS 22.280 sub-clause 3.1.
14.0.0
14.1.0
MCImp-MCCoRe
SP-73
SP-160543
S1-162019
22.280
0005
Rel-14
D
Editorial changes to MCCoRe TS 22.280 Informative Annex D sub-clause D.1
14.0.0
14.1.0
MCImp-MCCoRe
SP-73
SP-160543
S1-162020
22.280
0006
Rel-14
F
In MCCoRe TS 22.280 provide changes to References 1, 2, and 3 in clause 2.
14.0.0
14.1.0
MCImp-MCCoRe
SP-73
SP-160543
S1-162408
22.280
0007
1
Rel-14
D
Provide editorial changes to several sub-clauses in MCCoRe TS 22.280 for consistency and to improve understanding and readability.
MCC Note: 25th change (removing Annexes a, B and C) not implemented since contradicting other CRs (i.e. CR#0001r1, 0008r2, 0010r1, 0012r1 and 0021r1)
14.0.0
14.1.0
MCImp-MCCoRe
SP-73
SP-160543
S1-162497
22.280
0008
2
Rel-14
C
In MCCoRe TS 22.280 provide editorial changes to the service description in sub-clause 6.19.1 Call rejection and queuing.
14.0.0
14.1.0
MCImp-MCCoRe
SP-73
SP-160543
S1-162036
22.280
0009
Rel-14
B
In MCCoRe TS 22.280 Add a requirement in sub-clause 8.4.2 Requirements for a single group with multiple MCX Services.
14.0.0
14.1.0
MCImp-MCCoRe
SP-73
SP-160543
S1-162266
22.280
0010
1
Rel-14
B
In MCCoRe TS 22.280 Add sub-clause 7.4 requirements to normative Annex C MCCoRe Requirements for MCData.
14.0.0
14.1.0
MCImp-MCCoRe
SP-73
SP-160543
S1-162410
22.280
0012
1
Rel-14
F
Insertion of new clause 5.5.2 with requirement [R-5.1.8-002] from clause 5.1.8
14.0.0
14.1.0
MCImp-MCCoRe
SP-73
SP-160543
S1-162411
22.280
0013
1
Rel-14
F
Corrections to Clause 4.2
14.0.0
14.1.0
MCImp-MCCoRe
SP-73
SP-160543
S1-162124
22.280
0014
Rel-14
F
Correction of inconsistency between header 6.7 and overview text 6.7.1
14.0.0
14.1.0
MCImp-MCCoRe
SP-73
SP-160543
S1-162125
22.280
0015
Rel-14
F
Correction to clause 5.1.1 requirement [R-5.1.1-005]
14.0.0
14.1.0
MCImp-MCCoRe
SP-73
SP-160543
S1-162412
22.280
0016
1
Rel-14
F
Clarification of text in clause 5.4.1
14.0.0
14.1.0
MCImp-MCCoRe
SP-73
SP-160543
S1-162127
22.280
0017
Rel-14
F
Clarification of text in clause 5.6.1
14.0.0
14.1.0
MCImp-MCCoRe
SP-73
SP-160543
S1-162413
22.280
0018
1
Rel-14
F
Moving of informative text within requirements to NOTEs
14.0.0
14.1.0
MCImp-MCCoRe
SP-73
SP-160543
S1-162414
22.280
0019
1
Rel-14
F
Correction [R-7.12.3-003]
14.0.0
14.1.0
MCImp-MCCoRe
SP-73
SP-160543
S1-162415
22.280
0020
1
Rel-14
F
Correction of the entity that affiliates
14.0.0
14.1.0
MCImp-MCCoRe
SP-73
SP-160543
S1-162416
22.280
0021
1
Rel-14
F
Single requirement label [R-5.6.2.4.1-004] with two requirements
14.0.0
14.1.0
MCImp-MCCoRe
SP-73
SP-160543
S1-162132
22.280
0022
Rel-14
F
Corrections to definitions
14.0.0
14.1.0
MCImp-MCCoRe
SP-73
SP-160543
S1-162401
22.280
0023
1
Rel-14
F
Corrections to Group Regroup triggered by the need to support of Audio Cut-in capability
14.0.0
14.1.0
MCImp-MCCoRe
SP-74
SP-160891
S1-163008
22.280
0024
Rel-14
F
Corrections to referenced sub-clauses in Annex C
14.1.0
14.2.0
MCImp-MCCoRe
SP-74
SP-160891
S1-163009
22.280
0025
Rel-14
D
Editorial changes to 3 sub-clauses
14.1.0
14.2.0
MCImp-MCCoRe
SP-74
SP-160891
S1-163010
22.280
0026
Rel-14
D
Provide editorial changes to the service description in sub-clause 6.19.1 Communication rejection and queuing for readability.
14.1.0
14.2.0
MCImp-MCCoRe
SP-75
SP-170150
S1-170191
22.280
0027
1
Rel-14
F
Corrections to requirement references in the applicability annexes
14.2.0
14.3.0
MCImp-MCCoRe
SP-75
SP-170150
S1-171025
22.280
0030
Rel-14
F
Correct inconsistent use of the term 'one-to-many'
14.2.0
14.3.0
MCImp-MCCoRe
SP-76
SP-170445
S1-172428
22.280
0031
7
Rel-15
B
FRMCS Role management and presence
14.3.0
15.0.0
MONASTERY
SP-77
SP-170696
S1-173361
22.280
0042
1
Rel-15
F
Correction to requirement on usage of ulisted functional alias
15.0.0
15.1.0
MONASTERY
SP-77
SP-170696
S1-173362
22.280
0043
1
Rel-15
C
update requirement for functional alias
15.0.0
15.1.0
MONASTERY
SP-77
SP-170696
S1-173510
22.280
0045
2
Rel-15
C
update requirement for functional alias
15.0.0
15.1.0
MONASTERY
SP-78
SP-170985
S1-174042
22.280
0046
Rel-15
F
Updates to the wording in the specification to clarify that the requirements are applicable from LTE onwards
15.1.0
15.2.0
MCOver
SP-78
SP-170997
S1-174419
22.280
0047
2
Rel-16
B
Priority controlled by MCX User for receiving from Multiple MCX service Communication
15.1.0
16.0.0
MONASTERY2
SP-78
SP-170997
S1-174425
22.280
0049
3
Rel-16
B
Changes relating to the User regrouping section of 22.280
15.1.0
16.0.0
MONASTERY2
SP-79
SP-180134
S1-180037
22.280
0053
Rel-16
B
Enhanced control of User Regroup and Private Communication
16.0.0
16.1.0
MONASTERY2
SP-79
SP-180134
S1-180436
22.280
0057
1
Rel-16
F
Clarification of definition of Mission Critical Service in 22.280
16.0.0
16.1.0
MONASTERY2
SP-79
SP-180134
S1-180439
22.280
0060
1
Rel-16
B
Changes related to membership/affiliation section of 22.280
16.0.0
16.1.0
MONASTERY2
SP-79
SP-180134
S1-180564
22.280
0054
3
Rel-16
B
Adding more functionality to interworking between FRMCS and GSM-R
16.0.0
16.1.0
MONASTERY2
SP-79
SP-180134
S1-180565
22.280
0055
5
Rel-16
C
Functional Alias enhancements(chapter 5.9a)
16.0.0
16.1.0
FS_FRMCS2
SP-79
SP-180134
S1-180568
22.280
0056
2
Rel-16
B
Introduction of railway emergency alert functionality to 22.280
16.0.0
16.1.0
MONASTERY2
SP-79
SP-180134
S1-180583
22.280
0061
2
Rel-16
B
Changes related to administrative sections of 22.280
16.0.0
16.1.0
MONASTERY2
SP-79
SP-180134
S1-180612
22.280
0059
3
Rel-16
B
Query of location based on functional alias
16.0.0
16.1.0
MONASTERY2
SP-80
SP-180306
S1-181704
22.280
0083
2
Rel-16
A
Generalisation of EPS into 3GPP system
16.1.0
16.2.0
MCOver
SP-80
SP-180307
S1-181385
22.280
0063
1
Rel-16
A
User profile presentation priority
16.1.0
16.2.0
MCImp-MCCoRe
SP-80
SP-180310
S1-181582
22.280
0071
2
Rel-16
C
chapter_5_10 MCX User log in to multiple devices
16.1.0
16.2.0
MONASTERY2
SP-80
SP-180310
S1-181588
22.280
0074
2
Rel-16
F
Interworking between MCX Service system and GSM-R
16.1.0
16.2.0
MONASTERY2
SP-80
SP-180310
S1-181589
22.280
0070
2
Rel-16
B
Addition of location based comunication depending on functional alias
16.1.0
16.2.0
MONASTERY2
SP-80
SP-180310
S1-181590
22.280
0069
2
Rel-16
B
Adding authorization for private comunication based on functional alias
16.1.0
16.2.0
MONASTERY2
SP-80
SP-180310
S1-181617
22.280
0082
2
Rel-16
B
Add a requirement on 5.11 Location
16.1.0
16.2.0
MONASTERY2
SP-80
SP-180310
S1-181700
22.280
0073
4
Rel-16
B
Extension of functional alias chapter 5.9a
16.1.0
16.2.0
MONASTERY2
SP-80
SP-180310
S1-181705
22.280
0064
4
Rel-16
B
Addition of location functionality for autonomous train control and operation
16.1.0
16.2.0
MONASTERY2
SP-80
SP-180310
S1-181706
22.280
0065
4
Rel-16
F
Off-network UE functionality for virtual coupling
16.1.0
16.2.0
MONASTERY2
SP-81
SP-180757
S1-182255
22.280
0089
Rel-16
F
Public emergency calls
16.2.0
16.3.0
MONASTERY2
SP-81
SP-180757
S1-182561
22.280
0084
1
Rel-16
B
Dynamic Group Participation
16.2.0
16.3.0
MONASTERY2
SP-81
SP-180757
S1-182580
22.280
0090
1
Rel-16
F
Clarification of requirement R-6.4.9-001
16.2.0
16.3.0
MONASTERY2
SP-81
SP-180757
S1-182581
22.280
0088
2
Rel-16
B
Selection of Application Layer Priorities by the MCX Service user
16.2.0
16.3.0
MONASTERY2
SP-81
SP-180761
S1-182614
22.280
0085
1
Rel-16
B
Application of MCX Services to maritime usage
16.2.0
16.3.0
MARCOM
Change history
Date
Meeting
TDoc
CR
Rev
Cat
Subject/Comment
New version
2018-12
SP-82
SP-180999
0091
1
B
Requirement to allow for users to automatically be informed when affiliation information changes in a group
16.4.0
2018-12
SP-82
SP-181000
0094
1
B
Move interworking of functional alias from MCPTT to MCCoRe TS, MCCoRe part
16.4.0
2018-12
SP-82
SP-181000
0097
1
B
Interworking among MCX Service systems
16.4.0
2018-12
SP-82
SP-181000
0101
1
F
Dynamic Group Participation
16.4.0
2018-12
SP-82
SP-181000
0099
2
B
Unique addressing of MCX Users when using functional alias
16.4.0
2018-12
SP-82
SP-181000
0098
2
B
Additional requirements for the use of a gateway UE
16.4.0
2018-12
SP-82
SP-181000
0096
1
C
Changes to recording and audit metadata
16.4.0
2019-03
SP-83
SP-190079
0107
3
F
Clarification for discreet listening
16.5.0
2019-03
SP-83
SP-190084
0102
1
C
Group regrouping additional requirements
16.5.0
2019-06
SA#84
SP-190313
0110
1
C
Add new capabilities for late communication entry
17.0.0
2019-06
SA#84
SP-190313
0111
2
C
Deactivation of an unlisted functional alias and deactivation status
17.0.0
2019-06
SA#84
SP-190313
0108
2
C
Enhance metadata to be logged for Railway post-incident analysis
17.0.0
2019-09
SA#85
SP-190799
0133
1
A
Additional broadcast regroup requirements
17.1.0
2019-09
SA#85
SP-190799
0120
1
B
Additional broadcast regroup requirements
-> ignored (identical to the CR#0133r1 just above)
17.1.0
2019-09
SA#85
SP-190799
0129
2
A
Clarification of treatment of private call and private emergency calls to functional aliases activated by more than one MCX User
17.1.0
2019-09
SA#85
SP-190813
0122
1
C
Support the FRMCS use case for Arbitration when a user is registered to multiple UEs
17.1.0
2019-09
SA#85
SP-190813
0127
1
F
Extend Functional Alias binding to MCX Service Private Communication
17.1.0
2019-09
SA#85
SP-190813
0131
1
B
Support the location services related use cases while operating in off-network mode
17.1.0
2019-09
SA#85
SP-190813
0121
2
C
Activate Location Information report of a specific FA in a certain area
17.1.0
2019-09
SA#85
SP-190813
0126
1
F
Clarify routing location dependent communications as part of handling MCX Service Private Communication requests
17.1.0
2019-09
SA#85
SP-190813
0132
2
B
Support the recording of communication related use cases while operating in off-network mode
17.1.0
2019-09
SA#85
SP-190804
0134
1
F
New additional broadcast regroup requirements
17.1.0
2019-12
SA#86
SP-191030
0138
2
C
Clarification on interworking between FRMCS System and Public Networks
17.2.0
2019-12
SA#86
SP-191030
0137
1
D
Editorial correction to broadcast regroup requirements
17.2.0
2020-07
SA#88e
SP-200560
0140
3
A
Clarification on the maximum number limit of simultaneous log ins of an MCX user
17.3.0
2020-07
SA#88e
SP-200560
0141
F
Addition of a per-MCX user log-in limit
17.3.0
2020-12
SA#90e
SP-201029
143
1
B
Enhancement to MCX User request queue operation
17.4.0
2021-03
SA#91e
SP-210199
144
1
B
Gateway MCX UE identification
17.5.0
2021-06
SA#92e
SP-210499
0145
1
C
Enhancement of MCX UE de-affiliation requirements
17.6.0
2021-09
SA#93e
SP-211036
0147
F
Correction - Adding missing requirements into tables in the normative Annexes
17.7.0
2021-09
SA#93e
SP-211061
0146
1
B
Sharing administrative configuration between Mission Critical Organizations (SACI_MCS)
18.0.0
2021-09
SA#93e
SP-211074
0148
2
B
Ad hoc group call requirements (AHGC)
18.0.0
2022-03
SP#95e
SP-220082
0149
C
Enhanced MCX Service Ad hoc Group Communication to support Railway needs
18.1.0
2022-06
SA#96
SP-220434
152
1
F
Call restriction based on subparts/elements of functional alias
18.2.0
2022-06
SA#96
SP-220434
153
1
F
Additional parameters for Location Information and clarification of Location terms
18.2.0
2022-06
SA#96
SP-220434
154
1
F
Enhanced MCX Service Ad hoc Group Communication to support Railway needs
18.2.0
2022-12
SA#98
SP-221260
0157
D
Minor editorial modification on the definition of location
19.0.0
2023-03
SA#99
SP-230218
0159
1
A
Introduction of MCX Service Ad hoc Group Emergency Alert
19.1.0
2023-06
SA#100
SP-230526
0163
3
A
Notification of updated list of participants of Ad hoc Group Emergency Alert
19.2.0
2023-06
SA#100
SP-230522
0160
3
B
UE-to-UE Multi-hop relay requirements for mission critical communications
19.2.0
2023-09
SA#101
SP-231022
0165
1
C
Addition of requirements for Ad hoc Group Emergency Alert and for multiple MCX communications reception
19.3.0
2023-12
SA#102
SP-231395
0167
3
A
Enhancement of MCX Service Ad hoc Group Emergency Alert and Ad hoc Group Communications for railways
19.4.0
2023-12
SA#102
SP-231395
0166
2
D
Editorial correction: Move requirement from chapter 6.7.3 to chapter 6.15.6.2
19.4.0
2024-06
SA#104
SP-240789
0171
1
F
Clarification of non-3GPP devices using multiple MCX gateway UE
19.5.0
2024-09
SA#105
SP-241145
0172
2
F
Editorial correction: Delete R-6.15.6.2-004a from chapter 6.7.3
19.6.0
2025-03
SA#107
SP-250301
0173
F
Correction to Annex C
19.7.0
2025-03
SA#107
SP-250303
0176
1
B
Combining of Ad hoc Group calls
20.0.0
2025-09
SA#109
SP-250975
0179
1
C
Addition of Functional Aliases in the participants list and in the notifications of AHGCand authorizations for combining Ad hoc Group calls
20.1.0
2025-09
SA#109
SP-250975
0180
1
C
Addition of Functional Aliases in the notifications of AHG emergency alert and combining AHG emergency alerts
20.1.0
2025-09
SA#109
SP-250977
0177
1
C
Discreet listening clarifications
20.1.0
|
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 clause 8 should be used as guidance for MCData interworking between individual applications within that one MCX Service.
|
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 cope with the demands of simultaneous services. The requirements in sub-clause 8.2.2 identify how to handle simultaneous services which are intended to be completely independent of each other but limits in total capacity to handle multiple services and multiple instances within a service is left for suppliers to characterise for their products.
Where independent functionality between services is constrained due to transport capacity limitations, those requirements are indicated in the sub-clause on Priority between Services.
When the constraint is due to the service itself (e.g. Audio embedded within a video and MCPTT speech both delivering audible signals) any potential conflict may be avoided by action in the network part of the service but these actions are not specified. In sub-clause 8.2.2 actions taken by a single UE in case of conflict not resolved in the network are specified.
|
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 Service and receive on another without service interaction limitations.
[R-8.2.2-004] A user shall be able to transmit on different MCX Services at essentially the same time without service interaction limitations.
[R-8.2.2-005] A user shall be able to receive on different MCX Services at essentially the same time without service interaction limitations except where services are competing for the same unsharable resource which may include the display, audio transducers, etc.
[R-8.2.2-006] When operating multiple MCX Services on the same network, radio resources shall be able to be utilized in an efficient manner for all MCX Services up to certain thresholds defined for each MCX Service and/or the combination of MCX Services. The radio resource allocation for each MCX Service and the combination of MCX Services shall be flexible based on demand, or allocated in a predefined manner.
[R-8.2.2-007] The network shall be able to assign radio resources so that resources assigned to each MCX Service, or the combination of all MCX Services stays below a threshold, subject to the agreement between the 3GPP network operator and the Mission Critical Organization(s) (e.g., 3GPP network can be operated by Mission Critical Organization(s), or 3GPP network is operated by commercial operator), for resources to be used for MCX Services without impacting other non-MCX Services.
|
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 UE.
[R-8.3-003] The MCX Service shall provide a mechanism for a MCX User to prioritize the use of contended resources (e.g. display, loudspeaker) in the UE (e.g. most recently selected MCX Service, MCPTT voice always has priority).
[R-8.3-004] Communication marked as Emergency or Imminent Peril shall take priority use of contended resources in the UE over communication not marked as Emergency or Imminent Peril.
[R-8.3-005] When a MCX Service is denied access to contended resource in the UE, an indication shall be given to the User to alert them of the situation.
[R-8.3-006] When a MCX Service is denied access to contended resource in the UE, a facility shall be provided for the User to select their preferred MCX Service for access to contended resources for the duration of the limitation.
|
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 User may affiliate to a single group for two services, this could be a single affiliation indicating two services but handled together or it could be that the UE sends two affiliations, one for each service, in response to the single command to affiliate. There may also be other possibilities. In essence, the solution should look and feel like a combined service.
|
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 subset of MCX Services used by the group, or independently by MCX Service.
[R-8.4.2-003] To support operation coordinated between mission critical services, an MCX Service used by a mission critical group shall be able to interact with another MCX Service used by the same group.
[R-8.4.2-004] To support combined services where the operation is intended to be coordinated, each MCX Service shall be able to apply similar geographic restrictions in use for one MCX Service to also operate in the coordinated MCX Service(s).
[R-8.4.2-005] The MCX Service shall provide a mechanism by which an authorized MCX User who is affiliated to multiple MCX Services in a single group can de-affiliate specific MCX UEs from each MCX Service independently.
|
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 participate in a group e.g. choice of codec so that an MCX User can check the UE’s compatibility before attempting to affiliate.
[R-8.4.3.1-003] The MCX Service shall provide a mechanism for a UE to advertise its capability and limitation information when its MCX User affiliates to a group.
NOTE: For example when an MCX User affiliates to an MCVideo group, the MCX User’s UE may indicate the codecs and coding rates supported so that the MCVideo service will ensure that the UE receives video that it can render.
[R-8.4.3.1-004] If the MCX User affiliates to a group, but its UE does not provide capability and limitation information, then the MCX Service shall assume that any MCX Service relevant content can be handled by that UE.
|
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 provide transcoding for UEs that support the service but do not support the codec.
|
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 specific MCX Service.
[R-8.4.6-002] The MCX Service shall provide configuration and capability so that when a UE is affiliated to multiple groups and some or all of the groups periodically require location messages to be sent then each location message sent may be configured to apply to all affiliated groups or may be applied to only one specific group.
[R-8.4.6-003] The MCX Service shall provide configuration and capability so that when a UE is affiliated to multiple Common MCX Service Groups and some or all of the Common MCX Service Groups periodically require location messages to be sent then each location message sent may be configured to apply to all Common MCX Service Groups or may be applied to only one specific Common MCX Service Group.
|
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, priority management shall manage all data flows from the different mission critical services together when applying priority decisions.
NOTE 2: No mission critical service is considered as always having priority over another.
[R-8.5.2-003] The MCX Service systems shall provide a mechanism to dynamically prioritize one MCX Service over another.
[R-8.5.2-004] The MCX Services, in coordination with each other, shall be able to give appropriate priorities to the different communications according to User, content type, device type, participant type and operational situation.
[R-8.5.2-005] MCX Services shall notify users of actions taken by the dispatcher that result in a change in priority for a data flow.
9 Air ground air Communication
|
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 applicable to MCPTT.
Table A.1
5 MCX Service Requirements common for on the network and off the network
NA
5.1 General Group Communications Requirements
NA
5.1.1 General aspects
R-5.1.1-001
R-5.1.1-002
R-5.1.1-003
R-5.1.1-004
R-5.1.1-005
5.1.2 Group/status information
R-5.1.2-001
R-5.1.2-002
5.1.3 Group configuration
R-5.1.3-001
R5.1.3-002
5.1.4 Identification
R-5.1.4-001
5.1.5 Membership/affiliation
R-5.1.5-001
R-5.1.5-002
R-5.1.5-003
R-5.1.5-004
R-5.1.5-005
R-5.1.5-006
R-5.1.5-007
R-5.1.5-008
5.1.6 Group Communication administration
R-5.1.6-001
5.1.7 Prioritization
R-5.1.7-001
R-5.1.7-002
5.1.8 Charging requirements for MCX Service
R-5.1.8-001
R-5.1.8-003
R-5.1.8-004
R-5.1.8-005
R-5.1.8-006
R-5.1.8-007
R-5.1.8-008
R-5.1.8-009
R-5.1.8-010
R-5.1.8-011
5.1.9 MCX Service Emergency Alert triggered by location
NA
5.2 Broadcast Group
NA
5.2.1 General Broadcast Group Communication
R-5.2.1-001
R-5.2.1-002
5.2.2 Group-Broadcast Group (e.g., announcement group)
R-5.2.2-001
R-5.2.2-002
R-5.2.2-003
R-5.2.2-004
5.2.3 User-Broadcast Group (e.g., System Communication)
R-5.2.3-001
R-5.2.3-002
5.3 Late communication entry
R-5.3-001
R-5.3-002
R-5.3-003
R-5.3-004
R-5.3-005
5.4 Receiving from multiple MCX Service communications
5.4.1 Overview
NA
5.4.2 Requirements
R-5.4.2-001
R-5.4.2-002
R-5.4.2-003
R-5.4.2-004
R-5.4.2-004A
R-5.4.2-004B
R-5.4.2-005
R-5.4.2-006
R-5.4.2-007
R-5.4.2-007a
R-5.4.2-008
R-5.4.2-009
5.5 Private Communication
NA
5.5.1 Private Communication general requirements
NA
5.5.2 Charging requirement for MCX Service
R-5.5.2-001
5.6 MCX Service priority requirements
NA
5.6.1 Overview
NA
5.6.2 Communication types based on priorities
NA
5.6.2.1 MCX Service Emergency and Imminent Peril general requirements
NA
5.6.2.1.1 Overview
NA
5.6.2.1.2 Requirements
R-5.6.2.1.2-001
R-5.6.2.1.2-002
R-5.6.2.1.2-003
R-5.6.2.1.2-004
R-5.6.2.1.2-005
5.6.2.2 MCX Service Emergency Group Communication
NA
5.6.2.2.1 MCX Service Emergency Group Communication requirements
R-5.6.2.2.1-001
R-5.6.2.2.1-002
R-5.6.2.2.1-003
R-5.6.2.2.1-004
R-5.6.2.2.1-005
R-5.6.2.2.1-006
R-5.6.2.2.1-007
R-5.6.2.2.1-008
R-5.6.2.2.1-009
R-5.6.2.2.1-010
R-5.6.2.2.1-011
R-5.6.2.2.1-012
R-5.6.2.2.1-013
R-5.6.2.2.1-014
5.6.2.2.2 MCX Service Emergency Group Communication cancellation requirements
R-5.6.2.2.2-001
R-5.6.2.2.2-002
R-5.6.2.2.2-003
R-5.6.2.2.2-004
R-5.6.2.2.2-005
5.6.2.3 MCX Service Imminent Peril Group
NA
5.6.2.3.1 MCX Service Imminent Peril Group Communication requirements
R-5.6.2.3.1-001
R-5.6.2.3.1-002
R-5.6.2.3.1-003
R-5.6.2.3.1-004
R-5.6.2.3.1-005
R-5.6.2.3.1-006
R-5.6.2.3.1-007
R-5.6.2.3.1-008
R-5.6.2.3.1-009
5.6.2.3.2 MCX Service Imminent Peril Group Communications cancellation requirements
R-5.6.2.3.2-001
R-5.6.2.3.2-002
R-5.6.2.3.2-003
R-5.6.2.3.2-004
5.6.2.4 MCX Service Emergency Alert
NA
5.6.2.4.1 MCX Service Emergency Alert requirements
R-5.6.2.4.1-001
R-5.6.2.4.1-002
R-5.6.2.4.1-003
R-5.6.2.4.1-004
R-5.6.2.4.1-004a
R-5.6.2.4.1-005
R-5.6.2.4.1-006
R-5.6.2.4.1-007
R-5.6.2.4.1-008
R-5.6.2.4.1-009
R-5.6.2.4.1-010
R-5.6.2.4.1-011
R-5.6.2.4.1-012
R-5.6.2.4.1-013
5.6.2.4.2 MCX Service Emergency Alert cancellation requirements
R-5.6.2.4.2-001
R-5.6.2.4.2-002
R-5.6.2.4.2-003
5.7 MCX Service User ID
R-5.7-001
R-5.7-002
R-5.7-003
5.8 MCX UE Management
R-5.8-001
R-5.8-002
5.9 MCX Service User Profile
R-5.9-001
R-5.9-002
5.9A Functional alias
R-5.9a-001
R-5.9a-001a
R-5.9a-001b
R-5.9a-001c
R-5.9a-002
R-5.9a-002a
R-5.9a-003
R-5.9a-004
R-5.9a-005
R-5.9a-006
R-5.9a-007
R-5.9a-008
R-5.9a-009
R-5.9a-010
R-5.9a-011
R-5.9a-012
R-5.9a-013
R-5.9a-014
R-5.9a-015
R-5.9a-016
R-5.9a-017
R-5.9a-018
R-5.9a-019
R-5.9a-020
R-5.9a-021
R-5.9a-022
R-5.9a-023
[R-5.9a-024
R-5.9a-025
R-5.9a-026
R-5.9a-027
R-5.9a-028
R-5.9a-029
R-5.9a-030
R-5.9a-031
5.10 Support for multiple devices
R-5.10-001
R-5.10-001a
R-5.10-002
5.11 Location
R-5.11-001
R-5.11-002
R-5.11-002a
R-5.11-003
R-5.11-004
R-5.11-005
R-5.11-006
R-5.11-007
R-5.11-008
R-5.11-009
R-5.11-010
R-5.11-011
R-5.11-013
R-5.11-014
R-5.11-015
R-5.11-015
5.12 Security
R-5.12-001
R-5.12-002
R-5.12-003
R-5.12-004
R-5.12-005
R-5.12-006
R-5.12-007
R-5.12-008
R-5.12-009
R-5.12-010
R-5.12-011
R-5.12-012
R-5.12-013
R5-12-014
5.13 Media quality
R-5.13-001
5.14 Relay requirements
R-5.14-001
R-5.14-002
R-5.14-003
R-5.14-004
5.15 Gateway requirements
R-5.15-001
R-5.15-002
R-5.15-003
5.16 Control and management by Mission Critical Organizations
NA
5.16.1 Overview
NA
5.16.2 General requirements
R-5.16.2-001
R-5.16.2-002
R-5.16.2-003
R-5.16.2-004
R-5.16.2-005
5.16.3 Operational visibility for Mission Critical Organizations
R-5.16.3-001
5.17 General administrative – groups and users
R-5.17-001
R-5.17-002
R-5.17-003
R-5.17-004
R-5.17-005
R-5.17-006
R-5.17-007
R-5.17-008
5.18 Open interfaces for MCX services
NA
5.18.1 Overview
NA
5.18.2 Requirements
NA
5.19 Media forwarding
NA
5.19.1 Service description
NA
5.19.2 Requirements
NA
5.20 Receipt notification
NA
5.20.1 Service description
NA
5.20.2 Requirements
NA
5.21 Additional services for MCX Service communications
NA
5.21.1 Remotely initiated MCX Service communication
NA
5.21.1.1 Overview
NA
5.21.1.2 Requirements
NA
5.21.2 Remotely terminated MCX Service communication
NA
5.21.2.1 Requirements
R-5.21.2.1-001
6 MCX Service requirements specific to on-network use
NA
6.1 General administrative – groups and users
R-6.1-001
R-6.1-002
R-6.1-003
R-6.1-004
R-6.1-005
6.2 MCX Service communications
NA
6.2.1 Notification and acknowledgement for MCX Service Group Communications
NA
6.2.2 Queuing
R-6.2.2-001
R-6.2.2-002
R-6.2.2-003
R-6.2.2-004
R-6.2.2-005
R-6.2.2-006
6.3 General requirements
R-6.3-001
R-6.3-002
R-6.3-003
R-6.3-004
6.4 General group communication
NA
6.4.1 General aspects
R-6.4.1-001
6.4.2 Group status/information
R-6.4.2-005
R-6.4.2-001
R-6.4.2-002
R-6.4.2-003
R-6.4.2-004
R-6.4.2-006
R-6.4.2-007
6.4.3 Identification
R-6.4.3-001
R-6.4.3-002
6.4.4 Membership/affiliation
R-6.4.4-001
R-6.4.4-002
R-6.4.4-002a
R-6.4.4-003
R-6.4.4-004
6.4.5 Membership/affiliation list
R-6.4.5-001
R-6.4.5-002
R-6.4.5-003
R-6.4.5-003a
R-6.4.5-004
R-6.4.5-005
R-6.4.5-006
R-6.4.5-007
R-6.4.5-008
6.4.6 Authorized user remotely changes another MCX User’s affiliated and/or Selected MCX Service Group(s)
NA
6.4.6.1 Mandatory change
R-6.4.6.1-001
R-6.4.6.1-002
R-6.4.6.1-003
R-6.4.6.1-004
6.4.6.2 Negotiated change
R-6.4.6.2-001
R-6.4.6.2-002
R-6.4.6.2-003
R-6.4.6.2-004
R-6.4.6.2-005
R-6.4.6.2-006
6.4.7 Prioritization
R-6.4.7-001
R-6.4.7-002
R-6.4.7-003
R-6.4.7-004
6.4.8 Relay requirements
R-6.4.8-001
6.4.9 Administrative
R-6.4.9-001
R-6.4.9-002
R-6.4.9-003
R-6.4.9-004
R-6.4.9-005
R-6.4.9-006
6.5 Broadcast Group
NA
6.5.1 General Broadcast Group Communication
R-6.5.1-001
R-6.5.1-002
6.5.2 Group-Broadcast Group (e.g., announcement group)
R-6.5.2-001
6.5.3 User-Broadcast Group (e.g., system communication)
R-6.5.3-001
6.6 Dynamic group management (i.e., dynamic reporting)
NA
6.6.1 General dynamic regrouping
R-6.6.1-001
R-6.6.1-002
R-6.6.1-003
R-6.6.1-004
R-6.6.1-005
R-6.6.1-006
6.6.2 Group regrouping
NA
6.6.2.1 Service description
NA
6.6.2.2 Requirements
R-6.6.2.2-001
R-6.6.2.2-002
R-6.6.2.2-003
R-6.6.2.2-004
R-6.6.2.2-005
R-6.6.2.2-006
R-6.6.2.2-007
R-6.6.2.2-008
R-6.6.2.2-009
R-6.6.2.2-010
R-6.6.2.2-011
R-6.6.2.2-012
R-6.6.2.2-013
6.6.3 Temporary Broadcast Groups
R-6.6.3-001
R-6.6.3-001a
R-6.6.3-001b
R-6.6.3-002
6.6.4 User regrouping
NA
6.6.4.1 Service description
NA
6.6.4.2 Requirements
R-6.6.4.2-001
R-6.6.4.2-002
R-6.6.4.2-002a
R-6.6.4.2-002b
R-6.6.4.2-003
R-6.6.4.2-004
R-6.6.4.2-005
6.6.5 Dynamic Group Participation
NA
6.6.5.1 Service description
NA
6.6.5.2 Requirements
R-6.6.5.2-001
R-6.6.5.2-002
R-6.6.5.2-003
R-6.6.5.2-004
R-6.6.5.2-005
R-6.654.2-006
R-6.6.5.2-007
R-6.6.5.2-008
6.7 Private Communication
NA
6.7.1 Overview
NA
6.7.2 General requirements
R-6.7.2-001
R-6.7.2-002
R-6.7.2-003
R-6.7.2-004
R-6.7.2-005
R-6.7.2-006
6.7.3 Administrative
R-6.7.3-001
R-6.7.3-002
R-6.7.3-003
R-6.7.3-004
R-6.7.3-005
R-6.7.3-006
R-6.7.3-007
R-6.7.3-007a
R-6.7.3-008
6.7.4 Prioritization
R-6.7.4-001
R-6.7.4-002
R-6.7.4-003
R-6.7.4-004
R-6.7.4-005
R-6.7.4-006
R-6.7.4-007
6.7.5 Private Communication (without Floor control) commencement requirements
R-6.7.5-001
R-6.7.5-002
R-6.7.5-003
6.7.6 Private Communication (without Floor control) termination
R-6.7.6-001
R-6.7.6-002
6.8 MCX Service priority requirements
NA
6.8.1 General
R-6.8.1-001
R-6.8.1-002
R-6.8.1-003
R-6.8.1-004
R-6.8.1-005
R-6.8.1-006
R-6.8.1-007
R-6.8.1-008
R-6.8.1-009
R-6.8.1-010
R-6.8.1-011
R-6.8.1-012
R-6.8.1-013
R-6.8.1-014
R-6.8.1-015
R-6.8.1-016
6.8.2 3GPP system access controls
R-6.8.2-001
6.8.3 3GPP system admission controls
R-6.8.3-001
6.8.4 3GPP system scheduling controls
R-6.8.4-001
6.8.5 UE access controls
R-6.8.5-001
6.8.6 Mobility and load management
NA
6.8.6.1 Mission Critical mobility management according to priority
R-6.8.6.1-001
R-6.8.6.1-002
6.8.6.2 Load management
R-6.8.6.2-001
R-6.8.6.2-002
R-6.8.6.2-003
R-6.8.6.2-004
R-6.8.6.2-005
6.8.7 Application layer priorities
NA
6.8.7.1 Overview
NA
6.8.7.2 Requirements
R-6.8.7.2-001
R-6.8.7.2-002
R-6.8.7.2-003
R-6.8.7.2-004
R-6.8.7.2-005
R-6.8.7.2-006
R-6.8.7.2-007
R-6.8.7.2-008
R-6.8.7.2-009
R-6.8.7.2-010
6.8.8 Communication types based on priorities
NA
6.8.8.1 MCX Service Emergency Group Communication requirements
R-6.8.8.1-001
R-6.8.8.1-002
R-6.8.8.1-003
R-6.8.8.1-004
6.8.8.2 MCX Service Emergency Private Communication requirements
NA
6.8.8.3 Imminent Peril Group Communication requirements
R-6.8.8.3-001
R-6.8.8.3-002
R-6.8.8.3-003
6.8.8.4 MCX Service Emergency Alert
NA
6.8.8.4.1 Requirements
R-6.8.8.4.1-001
R-6.8.8.4.1-002
R-6.8.8.4.1-003
R-6.8.8.4.1-004
R-6.8.8.4.1-005
R-6.8.8.4.1-006
6.8.8.4.2 MCX Service Emergency Alert cancellation requirements
R-6.8.8.4.2-001
R-6.8.8.4.2-002
6.8.8.X Ad hoc Group Communication requirements
R-6.8.8.X-001
6.9 IDs and aliases
R-6.9-001
R-6.9-002
R-6.9-003
R-6.9-004
6.10 User Profile management
R-6.10-001
R-6.10-002
R-6.10-003
R-6.10-004
6.11 Support for multiple devices
R-6.11-001
R-6.11-002
R-6.11-003
6.12 Location
R-6.12-001
R-6.12-002
R-6.12-003
R-6.12-004
R-6.12-005
R-6.12-006
R-6.12-007
6.13 Security
NA
6.13.1 Overview
NA
6.13.2 Cryptographic protocols
R-6.13.2-001
R-6.13.2-002
R-6.13.2-003
6.13.3 Authentication
R-6.13.3-001
6.13.4 Access control
R-6.13.4-001
R-6.13.4-002
R-6.13.4-003
R-6.13.4-004
R-6.13.4-005
R-6.13.4-006
R-6.13.4-007
R-6.13.4-008
R-6.13.4-009
R-6.13.4-010
6.13.5 Regulatory issues
R-6.13.5-001
6.13.6 Storage control
NA
6.14 Interactions for MCX Service Group Communications and MCX Service Private Communications
R-6.14-001
R-6.14-002
6.15 Additional services for MCX Service communications
NA
6.15.1 Discreet listening capabilities
R-6.15.1-001a
R-6.15.1-001
R-6.15.1-002
R-6.15.1-002a
R-6.15.1-003
R-6.15.1-004
R-6.15.1-005
R-6.15.1-006
6.15.2 Ambient listening
NA
6.15.2.1 Overview of ambient listening
NA
6.15.2.2 Ambient listening requirements
NA
6.15.2.2.1 General ambient listening requirements
R-6.15.2.2.1-001
R-6.15.2.2.1-002
R-6.15.2.2.1-003
6.15.2.2.2 Remotely initiated ambient listening requirements
R-6.15.2.2.2-001
R-6.15.2.2.2-002
6.15.2.2.3 Locally initiated ambient listening requirements
R-6.15.2.2.3-001
R-6.15.2.2.3-002
6.15.3 Remotely initiated MCX Service Communication
NA
6.15.3.1 Overview
NA
6.15.3.2 Requirements
R-6.15.3.2-001
R-6.15.3.2-002
R-6.15.3.2-003
R-6.15.3.2-004
6.15.4 Recording and audit requirements
R-6.15.4-001
R-6.15.4-002
R-6.15.4-003
R-6.15.4-004
R-6.15.4-005
R-6.15.4-006
R-6.15.4-007
R-6.15.4-008
R-6.15.4-009
R-6.15.4-010
R-6.15.4-011
6.15.5 MCX Service Ad hoc Group Communication
NA
6.15.5.1 Overview
NA
6.15.5.2 General Aspects
R-6.15.5.2-001
R-6.15.5.2-001a
R-6.15.5.2-001b
R-6.15.5.2-001c
R-6.15.5.2-001d
R-6.15.5.2-002
R-6.15.5.2-003
R-6.15.5.2-004
R-6.15.5.2-005
R-6.15.5.2-006
R-6.15.5.2-007
R-6.15.5.2-008
R-6.15.5.2-009
R-6.15.5.2-010
R-6.15.5.2-011
R-6.15.5.2-012
R-6.15.5.2-013
R-6.15.5.2-014
R-6.15.5.2-014a
R-6.15.5.2-015
R-6.15.5.2-016
R-6.15.5.2-017
R-6.15.5.2-018
6.15.5.3 Administrative
R-6.15.5.3-001
R-6.15.5.3-002
R-6.15.5.3-003
R-6.15.5.3-004
R-6.15.5.3-005
R-6.15.5.3-006
6.15.5.4 Notification and acknowledgement for MCX Service Ad hoc Group Communications
R-6.15.5.4-001
R-6.15.5.4-001a
R-6.15.5.4-002
6.15.6 MCX Service Ad hoc Group Emergency Alert
NA
6.15.6.1 Overview
NA
|
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.
In the present document, modal verbs have the following meanings:
shall indicates a mandatory requirement to do something
shall not indicates an interdiction (prohibition) to do something
The constructions "shall" and "shall not" are confined to the context of normative provisions, and do not appear in Technical Reports.
The constructions "must" and "must not" are not used as substitutes for "shall" and "shall not". Their use is avoided insofar as possible, and they are not used in a normative context except in a direct citation from an external, referenced, non-3GPP document, or so as to maintain continuity of style when extending or modifying the provisions of such a referenced document.
should indicates a recommendation to do something
should not indicates a recommendation not to do something
may indicates permission to do something
need not indicates permission not to do something
The construction "may not" is ambiguous and is not used in normative elements. The unambiguous constructions "might not" or "shall not" are used instead, depending upon the meaning intended.
can indicates that something is possible
cannot indicates that something is impossible
The constructions "can" and "cannot" are not substitutes for "may" and "need not".
will indicates that something is certain or expected to happen as a result of action taken by an agency the behaviour of which is outside the scope of the present document
will not indicates that something is certain or expected not to happen as a result of action taken by an agency the behaviour of which is outside the scope of the present document
might indicates a likelihood that something will happen as a result of action taken by some agency the behaviour of which is outside the scope of the present document
might not indicates a likelihood that something will not happen as a result of action taken by some agency the behaviour of which is outside the scope of the present document
In addition:
is (or any other verb in the indicative mood) indicates a statement of fact
is not (or any other negative verb in the indicative mood) indicates a statement of fact
The constructions "is" and "is not" do not indicate requirements.
1 Scope
The present document describes service and performance requirements for ambient power-enabled Internet of Things (i.e. Ambient IoT). In the context of the present document, Ambient IoT device is an IoT device powered by energy harvesting, being either battery-less or with limited energy storage capability (e.g. using a capacitor) and the energy is provided through the harvesting of radio waves, light, motion, heat, or any other power source that could be seen suitable. An Ambient IoT device has low complexity, small size and lower capabilities and lower power consumption than previously defined 3GPP IoT devices (e.g. NB-IoT/eMTC devices). Ambient IoT devices can be maintenance free and can have long life span (e.g. more than 10 years).
The aspects addressed in this document include:
- Overview of Ambient IoT service and operation,
- Functional service requirements for Ambient IoT, including communication, positioning, management, exposure, charging, security and privacy.
- Performance service requirements for Ambient IoT, including inventory, sensors, tracking, and actuator.
NOTE: How Ambient IoT device performs energy harvesting is out of scope of this technical specification.
|
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.
- 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] 3GPP TS 22.368: "Service requirements for Machine-Type Communications (MTC)".
[3] 3GPP TS 22.278: "Service requirements for the Evolved Packet System (EPS)".
[4] 3GPP TS 22.261: "Service requirements for the 5G system".
[5] 3GPP TS 22.011: “Service accessibility”.
|
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 Internet of Things
RedCap Reduced Capability
|
2bcc1d4831fb70dd3621a5053d7410ff
|
22.369
|
4 Overview
| |
2bcc1d4831fb70dd3621a5053d7410ff
|
22.369
|
4.1 Introduction
|
In the 5G era, various IoT technologies [2][3][4][5] such as eMTC, NB-IoT, and RedCap have been developed to fulfil the increasing demand from verticals. These IoT technologies have achieved low cost, low power and massive connections and can meet requirements of many applications. However, there are still some use cases and applications that can benefit from an IoT technology that requires less power and has lower cost than previous IoT technologies. Improvements can be made where maintenance-free devices are required (e.g. where the devices are inaccessible and it is not possible to replace the device battery) or for devices in extreme environmental conditions. Finally, ultra-low complexity, very small device size/form factor (e.g. thickness of mm), longer life cycle, etc. are required for some use cases. Ambient IoT is a technology to fulfil these market requirements.
This Technical Specification describes the Ambient IoT technology service requirements as part of the 5G system to enable new services and use cases. Ambient IoT has the potential to benefit a large number of vertical industries, e.g. smart manufacturing, logistics and warehousing, smart grid, agriculture, and smart home by providing functionalities that fulfil the needs of industrial use cases. Therefore, a new kind of IoT service for the vertical industries will be enabled by combining Ambient IoT with cellular networks, vastly benefitting the 3GPP ecosystem.
|
2bcc1d4831fb70dd3621a5053d7410ff
|
22.369
|
4.2 Characteristics of Ambient IoT
|
Not all Ambient IoT devices are the same. Nevertheless, Ambient IoT devices have the following characteristics.
- Energy harvesting. An Ambient IoT device is an IoT device powered by energy harvesting, being either battery-less or with limited energy storage capability (e.g. using a capacitor). Energy is provided through harvesting of radio waves, light, motion, heat, or any other suitable power source. Energy harvesting can be continuous or incidental (e.g. based on the vibration that a vibration sensor has to report). It cannot be assumed that Ambient IoT devices always have enough power to initiate or receive communication.
- Low complexity. Ambient IoT devices are expected to have lower complexity, smaller size, reduced capabilities and lower power consumption than previously defined 3GPP IoT devices (e.g. NB-IoT/eMTC devices). Low complexity of Ambient IoT devices is also expected to be reflected in efficient use of network resources. In general, Ambient IoT applications will deploy very large numbers of Ambient IoT devices.
- Low data rates. Generally, Ambient IoT data transmissions contain only a low amount of data.
- Life span. Ambient IoT devices can be maintenance free and can have long life span (e.g. more than 10 years). However, the life span of an Ambient IoT device can also be relatively short, e.g. when tracking a package through a logistics chain.
- Communication characteristics. Ambient IoT devices can have a variety of communication characteristics, different from other IoT devices, based on how the Ambient IoT devices are powered by energy harvesting and whether / how the harvested energy can be stored. Ambient IoT devices will only be able to communicate when they have enough power. This can be an issue, especially when communication is initiated towards the Ambient IoT device, while it is not known whether the Ambient IoT device has enough power to receive this communication. For communications initiated by the Ambient IoT device, the Ambient IoT device cannot transmit data until it has harvested / stored enough energy. Some Ambient IoT devices can be powered on demand when they need to communicate. Additionally, some Ambient IoT devices will be able to communicate on a regular basis and have communication characteristics similar to regular IoT devices.
|
2bcc1d4831fb70dd3621a5053d7410ff
|
22.369
|
4.3 Typical Ambient IoT use cases
|
Ambient IoT can support many different use cases. Nevertheless, in general the Ambient IoT use cases can be characterised in four different use case categories:
- Inventory taking. With inventory taking, the main purpose is to discover what goods (e.g. boxes, containers, packages, tools) are present in a specific area. Upon request sent by the network within the specific area, Ambient IoT devices attached to these goods report an identifier associated with the good, possibly supplemented with other information such as status, measurement results and/or location.
- Sensor data collection. With sensor data collection, the Ambient IoT device is associated with a sensor. Transfer of sensor data can be initiated by the Ambient IoT device, e.g. periodically or when the Ambient IoT device has power, or can be triggered by the network.
- Asset tracking. With asset tracking, the main purpose is to determine the location of goods. Ambient IoT devices attached to these goods report an identifier associated with the good. This can then be combined with location information. Asset tracking can also be initiated by an Ambient IoT capable UE (i.e. a UE that can communicate with an Ambient IoT device), thus finding the location of Ambient IoT devices within a particular range of the UE.
- Actuator control. With actuator control, the Ambient IoT device is associated with an actuator. Transfer of actuator commands is generally initiated by the network.
|
2bcc1d4831fb70dd3621a5053d7410ff
|
22.369
|
4.4 Communication modes
|
Ambient IoT devices are expected to be able to communicate with the 5G network and/or Ambient IoT capable UE using the one or more of the following communication modes:
Ambient IoT Direct Network Communication: represents communication between the Ambient IoT device and 5G network with no UE conveying information between the Ambient IoT device and the 5G network.
Ambient IoT Indirect Network Communication: represents communication between the Ambient IoT device and the 5G network where there is an Ambient IoT capable UE helping in conveying information between the Ambient IoT device and the 5G network.
Ambient IoT device to UE direct Communication: represents communication between an Ambient IoT device and an Ambient IoT capable UE with no network entity in the middle.
Figures depicting these communication modes are presented below:
Figure 4.4-1: Ambient IoT Communication Modes
|
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.