hash
stringlengths 32
32
| doc_id
stringlengths 5
12
| section
stringlengths 4
595
| content
stringlengths 0
6.67M
|
|---|---|---|---|
20d3432075238c775cabdf9e701698cd | 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). |
20d3432075238c775cabdf9e701698cd | 22.280 | 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. |
20d3432075238c775cabdf9e701698cd | 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. |
20d3432075238c775cabdf9e701698cd | 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. |
20d3432075238c775cabdf9e701698cd | 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. |
20d3432075238c775cabdf9e701698cd | 22.280 | 7.7 Communication types based on priorities | |
20d3432075238c775cabdf9e701698cd | 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. |
20d3432075238c775cabdf9e701698cd | 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. |
20d3432075238c775cabdf9e701698cd | 22.280 | 7.7.3 Imminent Peril Communication | |
20d3432075238c775cabdf9e701698cd | 22.280 | 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. |
20d3432075238c775cabdf9e701698cd | 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. |
20d3432075238c775cabdf9e701698cd | 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. |
20d3432075238c775cabdf9e701698cd | 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. |
20d3432075238c775cabdf9e701698cd | 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. |
20d3432075238c775cabdf9e701698cd | 22.280 | 7.12 Streaming for ProSe UE-to-UE Relay and UE-to-Network Relay | |
20d3432075238c775cabdf9e701698cd | 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. |
20d3432075238c775cabdf9e701698cd | 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. |
20d3432075238c775cabdf9e701698cd | 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. |
20d3432075238c775cabdf9e701698cd | 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. |
20d3432075238c775cabdf9e701698cd | 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. |
20d3432075238c775cabdf9e701698cd | 22.280 | 7.15 Off-network UE-to-UE Relay | |
20d3432075238c775cabdf9e701698cd | 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. |
20d3432075238c775cabdf9e701698cd | 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. |
20d3432075238c775cabdf9e701698cd | 22.280 | 7.16 Off-network Ad hoc Group Communication | [R-7.16-001] The off-network MCX Service shall provide a mechanism to combine an ad hoc multiplicity of MCX Users within communication range into a group communication.
8 Inter-MCX Service interworking |
20d3432075238c775cabdf9e701698cd | 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. |
20d3432075238c775cabdf9e701698cd | 22.280 | 8.2 Concurrent operation of different MCX Services | |
20d3432075238c775cabdf9e701698cd | 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. |
20d3432075238c775cabdf9e701698cd | 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. |
20d3432075238c775cabdf9e701698cd | 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. |
20d3432075238c775cabdf9e701698cd | 22.280 | 8.4 Single group with multiple MCX Services | |
20d3432075238c775cabdf9e701698cd | 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. |
20d3432075238c775cabdf9e701698cd | 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. |
20d3432075238c775cabdf9e701698cd | 22.280 | 8.4.3 Compatibility of UE | |
20d3432075238c775cabdf9e701698cd | 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. |
20d3432075238c775cabdf9e701698cd | 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. |
20d3432075238c775cabdf9e701698cd | 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. |
20d3432075238c775cabdf9e701698cd | 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. |
20d3432075238c775cabdf9e701698cd | 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. |
20d3432075238c775cabdf9e701698cd | 22.280 | 8.5 Priority between services | |
20d3432075238c775cabdf9e701698cd | 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 |
20d3432075238c775cabdf9e701698cd | 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 |
20d3432075238c775cabdf9e701698cd | 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. |
20d3432075238c775cabdf9e701698cd | 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. |
20d3432075238c775cabdf9e701698cd | 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 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-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 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 6.15.5.4 Notification and acknowledgement for MCX Service Ad hoc Group Communications R-6.15.5.4-001 6.15.6 MCX Service Ad hoc Group Emergency Alert NA 6.15.6.1 Overview NA 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-005a R-6.15.6.2-005b R-6.15.6.2-006 R-6.15.6.2-007 R-6.15.6.2-008 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 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 7.16 Off-network Ad hoc Group Communication R-7.16-001 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 B (normative): MCCoRe Requirements for MCVideo Table B.1 provides an exhaustive list of those requirements in 3GPP TS 22.280 that are applicable to MCVideo. Table B.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 R-5.1.1-006 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 R-5.1.9-001 R-5.1.9-002 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 R-5.5.1-001 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-012 R-5.11-013 R-5.11-014 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 R-5.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 R-5.18.2-001 R-5.18.2-002 R-5.18.2-003 R-5.18.2-004 5.19 Media forwarding NA 5.19.1 Service description NA 5.19.2 Requirements R-5.19.2-001 R-5.19.2-002 R-5.19.2-003 5.20 Receipt notification NA 5.20.1 Service description NA 5.20.2 Requirements R-5.20.2-001 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 R-5.21.1.2-001 R-5.21.1.2-002 R-5.21.1.2-003 R-5.21.1.2-004 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 R-6.2.1-001 R-6.2.1-002 R-6.2.1-003 R-6.2.1-004 R-6.2.1-005 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-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.6.5.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 R-6.8.8.2-001 R-6.8.8.2-002 R-6.8.8.2-003 R-6.8.8.2-004 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.9 Ad hoc Group Communication requirements R-6.8.8.9-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 R-6.13.6-001 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 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-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 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 6.15.5.4 Notification and acknowledgement for MCX Service Ad hoc Group Communications R-6.15.5.4-001 6.15.6 MCX Service Ad hoc Group Emergency Alert NA 6.15.6.1 Overview NA 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-005a R-6.15.6.2-005b R-6.15.6.2-006 R-6.15.6.2-007 R-6.15.6.2-008 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 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 7.16 Off-network Ad hoc Group Communication R-7.16-001 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 C (normative): MCCoRe Requirements for MCData Table C.1 provides an exhaustive list of those requirements in 3GPP TS 22.280 that are applicable to MCData. Table C.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-006 5.1.2 Group/status information NA 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-005 R-5.1.5-007 R-5.1.5-008 5.1.6 Group Communication administration NA 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 R-5.1.9-001 R-5.1.9-002 5.2 Broadcast Group NA 5.2.1 General Broadcast Group Communication 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 NA 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-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 R-5.5.1-001 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-012 R-5.11-013 R-5.11-014 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 R-5.12-014 5.13 Media quality NA 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 R-5.18.2-001 R-5.18.2-002 R-5.18.2-003 R-5.18.2-004 5.19 Media forwarding NA 5.19.1 Service description NA 5.19.2 Requirements R-5.19.2-001 R-5.19.2-002 R-5.19.2-003 5.20 Receipt notification NA 5.20.1 Service description NA 5.20.2 Requirements R-5.20.2-001 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 R-5.21.1.2-001 R-5.21.1.2-002 R-5.21.1.2-003 R-5.21.1.2-004 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 R-6.2.1-001 R-6.2.1-002 R-6.2.1-003 R-6.2.1-004 R-6.2.1-005 6.2.2 Queuing NA 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-004 R-6.4.9-006 6.5 Broadcast Group NA 6.5.1 General Broadcast Group Communication NA 6.5.2 Group-Broadcast Group (e.g., announcement group) NA 6.5.3 User-Broadcast Group (e.g., system communication) NA 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-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.6.5.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 R-6.8.8.2-001 R-6.8.8.2-002 R-6.8.8.2-003 R-6.8.8.2-004 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.9 Ad hoc Group Communication requirements R-6.8.8.9-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 R-6.13.6-001 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 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-002 R-6.15.3.2-001 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-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 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 6.15.5.4 Notification and acknowledgement for MCX Service Ad hoc Group Communications R-6.15.5.4-001 6.15.6 MCX Service Ad hoc Group Emergency Alert NA 6.15.6.1 Overview NA 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-005a R-6.15.6.2-005b R-6.15.6.2-006 R-6.15.6.2-007 R-6.15.6.2-008 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 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 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 NA 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 NA 7.7.2 MCX Service Emergency Group Communication cancellation requirements NA 7.7.3 Imminent Peril Communication NA 7.7.3.1 Imminent Peril Group Communication requirements NA 7.7.3.2 Imminent Peril Group Communication cancellation requirements NA 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.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 |
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 |
2bcc1d4831fb70dd3621a5053d7410ff | 22.369 | 5 Functional service requirements of Ambient IoT | |
2bcc1d4831fb70dd3621a5053d7410ff | 22.369 | 5.1 General | The functional requirement for Ambient IoT service includes 6 aspects, i.e.
- Communication;
- Positioning/location;
- Management;
- Collected information and network capability exposure;
- Charging;
- Security and privacy
The Ambient IoT devices have some special characteristics such as Energy harvesting, Low complexity, Low data rates, Life span, and Reachability, etc.
Ambient IoT capable UEs are 3GPP UEs with the capability to communicate with an Ambient IoT device. |
2bcc1d4831fb70dd3621a5053d7410ff | 22.369 | 5.2 Functional service requirements of Ambient IoT | |
2bcc1d4831fb70dd3621a5053d7410ff | 22.369 | 5.2.1 Communication aspects | The 5G system shall be able to support 5G network or an Ambient IoT capable UE to communicate with a group of Ambient IoT devices simultaneously.
The 5G network shall support a mechanism to authorize an Ambient IoT capable UE to communicate with an Ambient IoT device.
The 5G system shall be able to support mechanisms to communicate:
- between an Ambient IoT device and the 5G network using Ambient IoT direct network communication or Ambient IoT indirect network communication, or
- between an Ambient IoT device and Ambient IoT capable UE using Ambient IoT device to UE communication.
NOTE: Examples of the communication between 5G network/Ambient IoT capable UE and Ambient IoT devices can include periodic sensor reporting or network-initiated inventory.
The 5G system shall provide suitable mechanisms to support communication between a trusted and authorized 3rd party and an Ambient IoT device or group of Ambient devices. |
2bcc1d4831fb70dd3621a5053d7410ff | 22.369 | 5.2.2 Positioning | The 5G system shall support location services for Ambient IoT devices (e.g., to locate Ambient IoT devices using absolute or relative positioning methods)
NOTE 1: The intention is not to use Ambient IoT devices to locate other Ambient IoT devices. |
2bcc1d4831fb70dd3621a5053d7410ff | 22.369 | 5.2.3 Management | The 5G network shall support suitable management mechanisms for an Ambient IoT device or a group of Ambient IoT devices.
The 5G system shall support a mechanism to:
- disable the capability to transmit RF signals for one or more Ambient IoT device that is / are currently able to transmit RF signals
- enable the capability to transmit RF signals for one or more Ambient IoT device that is / are currently disabled to transmit RF signals
Based on operator policy, the 5G system shall provide a suitable mechanism to permanently disable the capability of an Ambient IoT device or a group of Ambient IoT devices to transmit RF signals.
Subject to operator policy and regulatory requirements, the 5G system shall support suitable mechanisms for the Ambient IoT device to move between one or more networks and countries. |
2bcc1d4831fb70dd3621a5053d7410ff | 22.369 | 5.2.4 Exposure | Subject to user consent, operator policy and 3rd party request, the 5G system shall be able to obtain data from Ambient IoT devices (e.g. sensor data) and provide it to a trusted 3rd party via the 5G network.
Subject to user consent, operator’s policy and 3rd party request, the 5G system shall provide information about an Ambient IoT device or a group of Ambient IoT devices (e.g. position) to the trusted 3rd party via the 5G network.
The 5G system shall enable an authorized 3rd party to instruct the 5G network to trigger a group of Ambient IoT devices in an specific area and which action the Ambient IoT devices need to perform when triggered (e.g. send ID, receive further information, send measurement value). |
2bcc1d4831fb70dd3621a5053d7410ff | 22.369 | 5.2.5 Charging | The 5G system shall be able to collect charging information in a suitable way for using Ambient IoT services on per Ambient IoT device basis or a group of Ambient IoT devices (e.g., total number of communications per charging period). |
2bcc1d4831fb70dd3621a5053d7410ff | 22.369 | 5.2.6 Security and privacy | The 5G system shall enable security protection suitable for Ambient IoT, without compromising overall 5G security protection.
The 5G system shall be able to provide a mechanism to protect the privacy of information (e.g., location and identity) exchanged during communication between an Ambient IoT device and the 5G network or an Ambient IoT capable UE.
Based on subscription and operator policies, the 5G system shall authorize an Ambient IoT capable UE to communicate with a specific Ambient IoT device or with a group of Ambient IoT devices. |
2bcc1d4831fb70dd3621a5053d7410ff | 22.369 | 6 Performance service requirements of Ambient IoT | |
2bcc1d4831fb70dd3621a5053d7410ff | 22.369 | 6.1 General | Ambient IoT service can be categorized into 4 categories, namely inventory, sensor data collection, tracking and actuator control. The corresponding performance services requirements are listed in the following subclauses. |
2bcc1d4831fb70dd3621a5053d7410ff | 22.369 | 6.2 Performance service requirements for Inventory | Table 6.2-1 KPIs for inventory
Scenarios
Max. allowed end-to-end latency
Communication service availability
Reliability
User-experienced data rate
Message size
Device density
Communication range (Note 1)
Service area dimension
Device speed
Transfer interval
Positioning service latency
Positioning service availability
Positioning accuracy
Remark
Inventory or asset management
Typically, seconds level
99%
NA
<2 kbit/s
96/256 bits
<1.5 million devices/km²
indoor only
(Note 2)
30 m – 50 m indoor,
200 m - 400 m outdoor
1 km² – 10 km²
3 km/h – 10 km/h
NA
NA
NA
3 m indoor,
cell-level outdoor
NOTE 1: The communication range is the communication distance between the ambient IoT device and the 5G network or between the ambient IoT device and an ambient IoT capable UE.
NOTE 2: The device density is much lower in outdoors as only a subset of assets (e.g., stored indoors) will be in transit, and a much larger area for transit applies. |
2bcc1d4831fb70dd3621a5053d7410ff | 22.369 | 6.3 Performance service requirements for sensor data collection | Table 6.3-1 KPIs for sensor data collection
Deployment
Scenarios
Max. allowed end-to-end latency
Communication service availability
Reliability
User-experienced data rate
Message size
Device density
Communication range
(Note 1)
Service area dimension
Device speed
Transfer interval
Positioning service latency
Positioning service availability
Positioning accuracy
Remark
Indoor
Room environment monitoring (e.g. domicile, machinery)
20 s - 30 s
99 %
NA
<1 kbit/s
<100 bits
1.5 devices/m²
10 m - 30 m
NA
Stationary
NA
NA
NA
NA
Indoor agriculture and husbandry
>10 s
99.9%
NA
<1 kbit/s
Typically,
<1,000 bits
1 device /m²
30 m - 200 m
6,000 m² - 30,000 m²
Quasi-stationary
15 mins - 30 mins
NA
NA
NA
Outdoor
Smart grid
1 s
99%
NA
<1 kbit/s
Typically,
<800 bits
< 10,000 devices /km²
Typically, 50 m - 200 m
[several km² up to 100,000 km²]
Stationary
5 mins - 15 mins
NA
NA
several 10 m
Outdoor husbandry and logistics
Typically, > tens of seconds
99%
NA
<0.5 kbit/s
Typically,
[<800 bits]
<5,200 devices/ km²
[300 m - 500 m]
430,000 m²
≤ 3 km/h
15 mins
NA
NA
NA
Smart city
10 s - 30 s
99%
NA
<1 kbit/s
Typically,
<800 bits
<1,000 devices/ km²
300 m - 500 m
City wide including rural areas
Stationary
15 mins
NA
NA
NA
NOTE: The communication range is the communication distance between the ambient IoT device and the 5G network or between the ambient IoT device and an ambient IoT capable UE. |
2bcc1d4831fb70dd3621a5053d7410ff | 22.369 | 6.4 Performance service requirements for tracking | Table 6.4-1 KPIs for tracking
Deployment
Scenarios
Max. allowed end-to-end latency
Communication service availability
Reliability
User-experienced data rate
Message size
Device density
Communication range
(Note 1)
Service area dimension
Device speed
Transfer interval
Positioning service latency
Positioning service availability
Positioning accuracy
Remark
Indoor
Indoor tracking
1 s
99.9%
NA
<1 kbit/s
<1 kbits
25 devices /100 m²
-
250 devices /100 m²
10 m
200 m²
up to 3km/h
60 mins
1 s
90%
1 m - 3 m, 90% availability
Outdoor
Outdoor tracking
1 s
99.9%
NA
<1 kbit/s
<1 kbits
≤10 devices/ 100 m²
500 m
Up to the whole PLMN
up to 10 km/h
60 mins
1 s
95%
several 10 m
NOTE: The communication range is the communication distance between the ambient IoT device and the 5G network or between the ambient IoT device and an ambient IoT capable UE. |
2bcc1d4831fb70dd3621a5053d7410ff | 22.369 | 6.5 Performance service requirements for actuator control | Table 6.5-1 KPIs for actuator control Deployment Scenarios Max. allowed end-to-end latency Communication service availability Reliability User-experienced data rate Message size Device density Communication range (Note 1) Service area dimension Device speed Transfer interval Positioning service latency Positioning service availability Positioning accuracy Remark Indoor Indoor actuator control Several seconds 99% NA 2 kbit/s <100 Bytes <1.5 million/km² 50 m <250 m² for home, and 15,800 square meters for supermarket stationary 20 mins - 120 mins NA NA 3 m to 5 m indoor Outdoor Outdoor actuator control for large coverage Several seconds 99% N/A NA 128 bit (DL) NA [500] m outdoors 40,000 m2 - 4,000,000 m2 Static NA NA NA NA Outdoor actuator control for medium coverage Several seconds 99% NA <2 kbit/s <200 bits <20 devices/100 m² 200 m City wide including rural areas Static NA NA NA NA NOTE: The communication range is the communication distance between the ambient IoT device and the 5G network or between the ambient IoT device and an ambient IoT capable UE. Annex A (informative): Change history Change history Date Meeting TDoc CR Rev Cat Subject/Comment New version 2023-11 SA1#104 S1-233257 - Draft provided by editor. Note: corresponding WID not yet approved, so no official TS number 0.1.0 2023-12 SA#102 SP-231405 - MCC clean-up for presentation for one-step approval to SA. Corresponding WID to be submitted at the same time as this TS, then a TS number will be allocated. 1.0.0 2023-12 SA#102 SP-231750 - TR number known and added: TR 22.369 1.0.1 2023-12 SA#102 - Approved at SA#102 19.0.0 2024-03 SA#103 SP-240202 0001 3 F TS.22.369_adding the abbreviation 19.1.0 2024-06 SA#104 SP-240785 0006 1 D add the definition pointer of Ambient IoT device 19.2.0 2024-09 SA#105 SP-241145 0007 D Clarify that two Ambient IOT requirements are independent of each other 19.3.0 |
e8cee4e428329a7668584ba76bf8de13 | 22.837 | 1 Scope | The present document describes use cases and potential requirements for enhancement of the 5G system to provide sensing services addressing different target verticals/applications, e.g. autonomous/assisted driving, V2X, UAVs, 3D map reconstruction, smart city, smart home, factories, healthcare, maritime sector.
Use cases focus on NR-based sensing, while some use cases might make use of information already available in EPC and E-UTRA (e.g. cell/UE measurements, location updates). This study will not lead to impacts on EPC and E-UTRA. Some use cases could also include non-3GPP type sensors (e.g. Radar, camera).
The aspects addressed in the present document include collecting and reporting of sensing information, sensing related KPIs. Security, privacy, regulation and charging are additional topics of concern. |
e8cee4e428329a7668584ba76bf8de13 | 22.837 | 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] W. Favoreel, "Pedestrian sensing for increased traffic safety and efficiency at signalized intersections," 2011 8th IEEE International Conference on Advanced Video and Signal Based Surveillance (AVSS), 2011, pp. 539-542, doi: 10.1109/AVSS.2011.6027406.
[3] Advances in Wildlife Crossing Technologies: https://highways.dot.gov/public-roads/septoct-2009/advances-wildlife-crossing-technologies.
[4] Protection Detection: Making Roads Safe for Drivers and Wildlife: https://onlinepubs.trb.org/onlinepubs/webinars/201118.pdf.
[5] F. Liu et al., "Integrated Sensing and Communications: Towards Dual-functional Wireless Networks for 6G and Beyond," in IEEE Journal on Selected Areas in Communications, doi: 10.1109/JSAC.2022.3156632.
[6] T. S. Rappaport, G. R. MacCartney, M. K. Samimi and S. Sun, "Wideband Millimeter-Wave Propagation Measurements and Channel Models for Future Wireless Communication System Design," in IEEE Transactions on Communications, vol. 63, no. 9, pp. 3029-3056, Sept. 2015, doi: 10.1109/TCOMM.2015.2434384.
[7] C. Han, Y. Bi, S. Duan and G. Lu, "Rain Rate Retrieval Test From 25-GHz, 28-GHz, and 38-GHz Millimeter-Wave Link Measurement in Beijing," in IEEE Journal of Selected Topics in Applied Earth Observations and Remote Sensing, vol. 12, no. 8, pp. 2835-2847, Aug. 2019, doi: 10.1109/JSTARS.2019.2918507.
[8] IEEE 802.11-18/0611r16: “Wireless LANs, WiFi Sensing Uses Cases”
[9] TEM STANDARDS TEM STANDARDS AND RECOMMENDED PRACTICE: https://unece.org/fileadmin/DAM/trans/main/tem/temdocs/TEM-Std-Ed3.pdf
[10] S. Saponaraet. al, "Radar-on-Chip/in-Package in Autonomous Driving Vehicles and Intelligent Transport Systems: Opportunities and Challenges," inIEEE Sig. Proc. Mag., Sept. 2019.
[11] 3GPP TR 22.856, "Localized Mobile Metaverse Services".
[12] J. Hasch, E. Topak, R. Schnabel, T. Zwick, R. Weigel and C. Waldschmidt, "Millimeter-Wave Technology for Automotive Radar Sensors in the 77 GHz Frequency Band," inIEEE Transactions on Microwave Theory and Techniques, vol. 60, no. 3, pp. 845-860, March 2012.
[13] “Velodyne™ LiDAR VPL-16 User Manual,” 63-9243 Rev. E, Velodyne™ LiDAR, https://velodynelidar.com/wp-content/uploads/2019/12/63-9243-Rev-E-VLP-16-User-Manual.pdf.
[14] Liu, A., Huang, Z., Li, M., Wan, Y., Li, W., Han, T.X., Liu, C., Du, R., Tan, D.K.P., Lu, J. and Shen, Y., 2022. A survey on fundamental limits of integrated sensing and communication. IEEE Communications Surveys & Tutorials, 24(2), pp.994-1034.
[15] https://medium.com/desn325-emergentdesign/s-l-a-m-and-optical-tracking-for-xr-cfabb7dd536f.
[16] Dwivedi, S., Shreevastav, R., Munier, F., Nygren, J., Siomina, I., Lyazidi, Y., Shrestha, D., Lindmark, G., Ernström, P., Stare, E. and Razavi, S.M., 2021. Positioning in 5G networks. IEEE Communications Magazine, 59(11), pp.38-44.
[17] T. Murakami et al, “Wildlife Detection System Using Wireless LAN Signal,” in NTT Technical Review vol.17, No.6, pp. 45-48, June 20019, https://www.ntt-review.jp/archive/ntttechnical.php?contents=ntr201906fa13.pdf&mode=show_pdf.
[18] Eradication of elephant mortality and injury due to railway accidents through automatic tracking and alert system in IEEE Conference Publication, IEEE Xplore
[19] Impact of wild animals (deer and bears) on train operations 210616_KO_Animal2.pdf (jrhokkaido.co.jp) (in Japanese) [z] Rail Industry Safety Induction Handbook: https://railsafe.org.au/__data/assets/pdf_file/0009/32022/Rail-Industry-Safety-Induction-RISI-Handbook-V5.1.pdf.
[20] S. M. Patole, M. Torlak, D. Wang and M. Ali, "Automotive radars: A review of signal processing techniques," inIEEE Signal Processing Magazine, vol. 34, no. 2, pp. 22-35, March 2017.
[21] Society of Automotive Engineers (SAE), “Taxonomy and definition for terms related to Driving automation systems for on-Road Motor Vehicles”, https://www.sae.org/standards/content/j3016_202104/.
[22] Census of Fatal Occupational Injuries Summary, 2020, https://www.bls.gov/news.release/cfoi.nr0.htm.
[23] Javed MA, Muram FU, Hansson H, Punnekkat S, Thane H. Towards dynamic safety assurance for Industry 4.0. Journal of Systems Architecture. 2021 Mar 1; 114:101914.
[24] American National Standards Institute/Industrial Truck Safety Development Foundation, Safety standard for driverless, automatic guided industrial vehicles and automated functions of manned industrial vehicles, December 2019, 2019, [Online] http://www.itsdf.org.
[25] Moore, Erik George, "Radar Detection, Tracking and Identification for UAV Sense and Avoid Applications" (2019). Electronic Theses and Dissertations. 1544.
[26] https://www.bosch-mobility-solutions.com/en/solutions/assistance-systems/blind-spot-detection/.
[27] Soatti, Gloria, et al. "Enhanced vehicle positioning in cooperative ITS by joint sensing of passive features." 2017 IEEE 20th International Conference on Intelligent Transportation Systems (ITSC). IEEE, 2017.
[28] 5GAA_White_Paper_C-V2X Use Cases Volume II: Examples and Service Level Requirements.
[29] https://www.ieee802.org/11/Reports/tgbf_update.htm.
[30] https://mentor.ieee.org/802.11/dcn/20/11-20-1712-02-00bf-wifi-sensing-use-cases.xlsx.
[31] X. Liu, J. Cao, S. Tang and J. Wen, "Wi-Sleep: Contactless Sleep Monitoring via WiFi Signals," 2014 IEEE Real-Time Systems Symposium, 2014, pp. 346-355, doi: 10.1109/RTSS.2014.30.
[32] Chen V C. The micro-Doppler effect in radar. Artech house, 2019.
[33] 3GPP TS 22.261: “Service requirements for the 5G system”.
[34] A. Chebrolu, "FallWatch: A Novel Approach for Through-Wall Fall Detection in Real-Time for the Elderly Using Artificial Intelligence", 2021 Third International Conference on Transdisciplinary AI (TransAI), 2021, pp. 57-63, doi: 10.1109/TransAI51903.2021.00018, https://ieeexplore.ieee.org/document/9565618.
[35] B. A. Alsaify et al., “A CSI-Based Multi-Environment Human Activity Recognition Framework” Applied Sciences 12, no. 2: 930, 2022. https://doi.org/10.3390/app12020930.
[36] U. Saeed U et al., "Discrete Human Activity Recognition and Fall Detection by Combining FMCW RADAR Data of Heterogeneous Environments for Independent Assistive Living", Electronics 10(18):2237, 2021. https://doi.org/10.3390/electronics10182237.
[37] C. Dou, H. Huan, "Full Respiration Rate Monitoring Exploiting Doppler Information with Commodity Wi-Fi Devices". Sensors 21, 3505, 2021. https://doi.org/10.3390/s21103505.
[38] J. Pu, H. Zhang, "RF-Heartbeat: Robust and Contactless Heartbeat Monitoring Based on FMCW Radar", 2021. TechRxiv Preprint. https://doi.org/10.36227/techrxiv.15021645.v2.
[39] H. V. Habi and H. Messer, “Recurrent Neural Network for Rain Estimation Using Commercial Microwave Links,” in IEEE Transactions on Geoscience and Remote Sensing, vol. 59, no. 5, pp. 3672-3681, May 2021, doi: 10.1109/TGRS.2020.3010305.
[40] Roberto Opromolla, etc., “Perspectives and Sensing Concepts for Small UAS Sense and Avoid”, 2018 IEEE/AIAA 37th Digital Avionics Systems Conference (DASC).
[41] https://www.rwjbh.org/trinitas-regional-medical-center/treatment-care/sleep-disorders/sleep-apnea/.
[42] https://my.clevelandclinic.org/health/articles/10881-vital-signs.
[43] 3GPP TR 22.855, "Study on Ranging-based Services".
[44] Guoxuan Chi, et. al., "Wi-Drone: Wi-Fi-based 6-DoF Tracking for Indoor Drone Flight Control", MobiSys 22, Association for Computing Machinery, 2022.
[45] Report on Automated Valet Parking: technology assessment and use case implementation description – 5G Automotive Association (5gaa.org). https://5gaa.org/news/report-on-automated-valet-parking-technology-assessment-and-use-case-implementation-description/.
[46] Nie Y B , Zhang L . Main amendments to Working Safety Regulation of State Grid Company(Dynamical Part for Hydrodynamic Power Plant)[J]. East China Electric Power, 2008.
[47] Giuseppe Fragapane, René de Koster, Fabio Sgarbossa, Jan Ola Strandhagen, Planning and control of autonomous mobile robots for intralogistics: Literature review and research agenda, European Journal of Operational Research, Volume 294, Issue 2,2021, Pages 405-426.
[48] Li S, Li X, Lv Q, et al. WiFit: Ubiquitous bodyweight exercise monitoring with commodity wi-fi devices, 2018 IEEE SmartWorld, Ubiquitous Intelligence & Computing, Advanced & Trusted Computing, Scalable Computing & Communications, Cloud & Big Data Computing, Internet of People and Smart City Innovation, IEEE, 2018: 530-537.
[49] https://www.synopsys.com/automotive/autonomous-driving-levels.html.
[50] R. Bosch, “LRR3 3rd Generation Long-Range Radar Sensor,” Robert Bosch GmbH, Germany, 2009.
[51] Continental, A.G., ARS 408-21 Premium Long RangeRadar Sensor 77 GHz.ARS, pp.408-21.
[52] F. Engels et. al, "Automotive Radar Signal Processing: Research Directions and Practical Challenges," in IEEE JSTSP, June2021.
[53] I. Greshamet al., "Ultra-wideband radar sensors for short-range vehicular applications," inIEEE Transactions on Microwave Theory and Techniques, vol. 52, no. 9, pp. 2105-2122, Sept. 2004.
[54] AinsteinAutomotive Safety Radar T-79 short-range radar: https://ainstein.ai/vehicle-radar/short-range-wideband-high-resolution-automotive-radar-sensor/.
[55] National Academies of Sciences, Engineering, and Medicine. 1995. Virtual Reality: Scientific and Technological Challenges. Washington, DC: The National Academies Press. https://doi.org/10.17226/4761. |
e8cee4e428329a7668584ba76bf8de13 | 22.837 | 3 Definitions of terms, symbols and abbreviations | |
e8cee4e428329a7668584ba76bf8de13 | 22.837 | 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].
3GPP sensing data: data derived from 3GPP radio signals impacted (e.g. reflected, refracted, diffracted) by an object or environment of interest for sensing purposes, and optionally processed within the 5G system.
5G Wireless sensing: 5GS feature providing capabilities to get information about characteristics of the environment and/or objects within the environment (e.g. shape, size, orientation, speed, location, distances or relative motion between objects, etc) using NR RF signals and, in some cases, previously defined information available in EPC and/or E-UTRA.
Human motion rate accuracy describes the closeness of the measured value of the human body movement frequency caused by part(s) (e.g. chest) of the target object (i.e. human body) to the true value of the human body movement frequency.
non-3GPP sensing data: data provided by non-3GPP sensors (e.g. video, LiDAR, sonar) about an object or environment of interest for sensing purposes.
Sensing assistance information: information that is provided to 5G system and can be used to derive sensing result. This information does not contain 3GPP sensing data.
NOTE 1: Examples of sensing assistance information are map information, area information, a UE ID attached to or in the proximity of the sensing target, UE position information, UE velocity information and etc.
Sensing contextual information: information that is exposed with the sensing results by 5G system to a trusted third party which provides context to the conditions under which the sensing results were derived. This information does not contain 3GPP sensing data.
NOTE 2: Examples includes map information, area information, time of capture, UE location and ID. This contextual information can be required in scenarios where the sensing result is to be combined with data from other sources outside the 5GS.
Sensing group: a set of sensing transmitters and sensing receivers whose location is known and whose sensing data can be collected synchronously.
Sensing measurement process: process of collecting sensing data.
Sensing receiver: a sensing receiver is an entity that receives the sensing signal which the sensing service will use in its operation. A sensing receiver is an NR RAN node or a UE. A Sensing receiver can be located in the same or different entity as the Sensing transmitter.
Sensing result: processed 3GPP sensing data requested by a service consumer.
Sensing signals: Transmissions on the 3GPP radio interface that can be used for sensing purposes.
NOTE 3: The definition refers to NR RF signals and, in some cases, previously defined information available in EPC and/or E-UTRA can be used, without leading to impacts on EPC and E-UTRA.
Sensing transmitter: a sensing transmitter is the entity that sends out the sensing signal which the sensing service will use in its operation. A Sensing transmitter is an NR RAN node or a UE. A Sensing transmitter can be located in the same or different entity as the Sensing receiver.
Target sensing service area: a cartesian location area that needs to be sensed by deriving characteristics of the environment and/or objects within the environment with certain sensing service quality from the impacted (e.g. reflected, refracted, diffracted) wireless signals. This includes both indoor and outdoor environments.
Moving target sensing service area: the case where a target sensing service area is moving according to the mobility of a target from sensing transmitter’s perspective.
Transparent sensing: sensing measurements are communicated such that they can be discerned and interpreted by the 5G system, e.g. the data is communicated using a standard protocol to an interface defined by the 5G system.
The following KPIs apply to the definition of the use cases on sensing quantitative requirements:
- Accuracy of positioning estimate describes the closeness of the measured sensing result (i.e. position) of the target object to its true position value. It can be further derived into a horizontal sensing accuracy – referring to the sensing result error in a 2D reference or horizontal plane, and into a vertical sensing accuracy – referring to the sensing result error on the vertical axis or altitude.
- Accuracy of velocity estimate describes the closeness of the measured sensing result (i.e. velocity) of the target object’s velocity to its true velocity.
- Confidence level describes the percentage of all the possible measured sensing results that can be expected to include the true sensing result considering the accuracy.
- Sensing Resolution describes the minimum difference in the measured magnitude of target objects (e.g. range, velocity) to be allowed to detect objects in different magnitude.
- Missed detection probability is the conditional probability of not detecting the presence of target object/environment when the target object/environment is present. This probability is denoted by the ratio of the number of events falsely identified as negative, over the total number of events with a positive state. It applies only to binary sensing results.
NOTE 4: An event with a positive state refers to the presence of the characteristics of a target object or environment, including the event falsely identified as being negative and truly identified as being positive
- False alarm probability is the conditional probability of falsely detecting the the presence of target object/environment when the target object/environment is not present. This probability is denoted by the ratio of the number of events falsely identified as being positive, over the total number of events with a negative state. It applies only to binary sensing results.
NOTE 5: An event with a negative state refers to the non-presence of the characteristics of a target object or environment, including the event falsely identified as being positive and truly identified as being negative
- Max sensing service latency: time elapsed between the event triggering the determination of the sensing result and the availability of the sensing result at the sensing system interface.
- Refreshing rate: rate at which the sensing result is generated by the sensing system. It is the inverse of the time elapsed between two successive sensing results. |
e8cee4e428329a7668584ba76bf8de13 | 22.837 | 3.2 Symbols | For the purposes of the present document, the following symbols apply:
<symbol> <Explanation> |
e8cee4e428329a7668584ba76bf8de13 | 22.837 | 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].
<ABBREVIATION> <Expansion> |
e8cee4e428329a7668584ba76bf8de13 | 22.837 | 4 Overview | 5G Wireless sensing is a technology enabler to acquire information about characteristics of the environment and/or objects within the environment, that uses radio waves to determine the distance (range), angle, or instantaneous linear velocity of objects, etc. The 5G wireless sensing service relies on analyzing the transmissions, reflections, and scattering of wireless sensing signals.
This technical report investigates the potential of integrated sensing and communication technology for enabling new services and use cases for various industries. 5G wireless sensing service, as part of a cellular network provides new possibilities for enhanced usage of the telecommunication infrastructure in areas of object detection and tracking, environment monitoring and human motion monitoring. It provides input to various verticals - UAVs, smart home, V2X, factories.
The use cases examined in the report cover a wide range of applications, including:
• Object and intruder detection for smart home, on a highway, for railways, for factory, for predefined secure areas around critical infrastructure
• Collision avoidance and trajectory tracking of UAVs, vehicles, AGVs
• Automotive maneuvering and navigation
• Public safety search and rescue
• Rainfall monitoring and flooding
• Health and sports monitoring
Use cases focus is on 5G wireless sensing and some of the use cases could include non-3GPP type sensors (e.g. Radar, camera).
5G wireless sensing service also brings challenges related to confidentiality and privacy. There is a need to protect the sensing data from unauthorized access, interception and eavesdropping, but also to make sure there is compliance with regulation and user awareness.
In summary, it is considered beneficial for 3GPP specifications to address 5G system support of different use cases and service requirements for Integrated Sensing and Communication. |
e8cee4e428329a7668584ba76bf8de13 | 22.837 | 5 Use cases | |
e8cee4e428329a7668584ba76bf8de13 | 22.837 | 5.1 Use case of intruder detection in smart home | |
e8cee4e428329a7668584ba76bf8de13 | 22.837 | 5.1.1 Description | Sensing in smart home is a kind of the typical scenarios of indoor/local-area sensing [8]. Considering people spends most of lifetime indoor, how to improve the user experience for indoor scenario is important. Nowadays, various 5G UEs, e.g. wearable device, sensor, smart phone and customer premise equipment (CPE), are deployed at home. In order to enjoy more comfortable and convenient indoor life, various devices are connected via wireless signals to build a smart home platform.
In addition to communication purposes, wireless signals can also be used for sensing, e.g., monitoring the home environment continuously.
For intruder detection in smart home scenario, due to the activities of indoor object or human, the 3GPP signal measured by UE or network would be influenced. By analysing and collecting the sensing information such as Doppler frequency shift, amplitude change and phase change, the behaviour of indoor object or human could be detected as shown in following figure 5.1.1-1 which takes sensing entity that transceives (transmits and receives) the signal case as example.
.
Figure 5.1.1-1 An example of sensing operation of UE |
e8cee4e428329a7668584ba76bf8de13 | 22.837 | 5.1.2 Pre-conditions | Mary and her husband Tom live in a house with little daughter Alice.
On every working day, Mary and Tom have to leave home to work, and Alice needs to go to school. Since the community where the house is located is not stable, Mary and Tom have concern on the safety of their property.
In order to address their concerns, considering protecting the personal privacy and save family cost, Mary sets up some 5G CPEs (i.e. UE) in each room at home, which support sensing functionalities. |
e8cee4e428329a7668584ba76bf8de13 | 22.837 | 5.1.3 Service Flows | Mary and all her family members travel to Hawaii in a holiday. At this time, her house is empty. Since she worries about the safety of property, she enables the sensing service on intruder detection of the 5G CPEs (i.e. UE) at home.
Mary’s CPE (i.e. UE) in the living room is activated to perform the sensing operation. While the 5G CPE transmit 5G signals to provide communication services at home, the reflected signals are also received and measured at the CPE as sensing information. The CPE reports the sensing information to 5G network or further process locally. Via the analysing the differences between the 5G signals and the received reflected signals provided by sensing service performed by 5G system, any potential intruder will not be missed.
Also, Mary’s CPE in the living room can work with other 5G UEs in other rooms. The CPE discovers that the living room has another 5G device (i.e. UE) which could assist the sensing service as secondary device via direct device connection. The connectivity used in this case is direct device connection, and CPE and this 5G device play as the role of transmitter and receiver, respectively. The receiver measures the 5G signal (e.g., number of detected transmission paths), then provides sensing information to 5G network or further process locally. Via the analysing the differences between the 5G signals and the received reflected signals provided by sensing service performed by 5G system, any potential intruder will not be missed.
An intruder breaks into Mary’s house someday. The sensing service provided by 5G network system assists detecting that the presence of an intruder based on analysing the change of collected signals is aligned with the known feature of the activities of indoor human, and the alarm of intruder is sent to Mary’s smart phone. Mary calls the police for help, and the property is protected. |
e8cee4e428329a7668584ba76bf8de13 | 22.837 | 5.1.4 Post-conditions | Thanks to the sensing service provided by 5G UE and network, an intruder is found when Mary is out of home. |
e8cee4e428329a7668584ba76bf8de13 | 22.837 | 5.1.5 Existing features partly or fully covering the use case functionality | None. |
e8cee4e428329a7668584ba76bf8de13 | 22.837 | 5.1.6 Potential New Requirements needed to support the use case | [PR 5.1.6-1] The 5G network shall provide a mechanism for an operator to authorize a UE for sensing, e.g., based on location.
[PR 5.1.6-2] The 5G system shall support a UE to perform sensing measurement process based on the trusted third-party’s request.
[PR 5.1.6-3] The 5G system shall provide mechanisms for an operator to only collect or expose the sensing information requested by a trusted third-party according to agreement.
[PR 5.1.6-4] The 5G system shall support UE to perform sensing measurement process using signals received from other UE(s).
[PR 5.1.6-5] The 5G system shall support UE to perform sensing measurement process in licensed or unlicensed band.
[PR 5.1.6-6] The 5G system shall be able to provide the sensing service with following KPIs:
Table 5.1.6-1 Performance requirements of sensing results for intruder detection in smart home
Scenario
Sensing service area
Confidence level [%]
Accuracy of positioning estimate by sensing (for a target confidence level)
Accuracy of velocity estimate by sensing (for a target confidence level)
Sensing resolution
Max sensing service latency[ms]
Refreshing rate [s]
Missed detection [%]
False alarm [%]
Horizontal
[m]
Vertical
[m]
Horizontal
[m/s]
Vertical
[m/s]
Range resolution
[m]
Velocity resolution (horizontal/ vertical)
[m/s x m/s]
Intruder detection in smart home
Indoor
95
≤10
≤10
N/A
N/A
N/A
N/A
<1000
< 1
< 5
< 2
NOTE: The terms in Table 5.1.6-1 are found in Section 3.1.
NOTE: In this use case UE is acting as sensing transmitter and/or sensing receiver. This is an example and other options can also be valid. |
e8cee4e428329a7668584ba76bf8de13 | 22.837 | 5.2 Use case on pedestrian/animal intrusion detection on a highway | |
e8cee4e428329a7668584ba76bf8de13 | 22.837 | 5.2.1 Description | Transportation as a basic and essential industry plays one of the important roles in a human’s life. Making transportation smarter can make life more convenient and benefit economic development. Highways are an important part of smart transportation. Due to the strong road safety demand on smart transportation, it is necessary to monitor the road situation so as to make appropriate management of road traffic, give guidance or assistance information to vehicles and/or highway traffic safety administration [2].
For example, major accidents caused by pedestrians or animals crossing highways occur frequently [3] [4]. Currently, the highway supervision systems are mainly based on traditional sensors (e.g. radars, cameras) equipped in the roadside infrastructure, but there are still many problems in road supervision system, e.g. it only has partial coverage along the roadside, and the radar may be dedicated for a single usage which requires deploying different types of transportation radars in the same place to satisfy the respective sense use cases and requirements in the area of interest.
Base stations on the roadside are already used to provide 5G coverage for communication, and the radio signals can also be used to sense the environment for object detection.
The assumption of this use case is the following:
- There is at least 10km long and 33m wide dual three-lane carriageway, which has a central reservation to separate the carriageways, six 3.75m wide lanes and two 3.00m wide shoulders to permit emergency stops [9].
- The size and typical velocity of traffic participant is described in the Table 5.2.1-1.
Table 5.2.1-1
Size
(Length x Width x Height)
Typical velocity
Pedestrian
(Adult)
0.5m x 0.5m x 1.75m
5km/h [9]
Animal
(Sheep/deer)
1.5m x 0.5m x 1 m
5km/h [9]
Vehicle
4m x 1.75m x 1.5m
60km/h - 120km/h
As described in the figure 5.2.1-1, when the pedestrian/animal standing at the outermost side of the shoulder starts walking on the traffic lane, it means the highway intrusion happens. The distance that pedestrian/animal move perpendicular to the traffic lane (i.e. y direction in the figure 5.2.1-1) is more sensitive for road safety, compared to the distance parallel to the traffic lane (i.e. x direction in the figure 5.2.1-1).
Figure 5.2.1-1: Intrusion detection on a dual three-lane carriageway |
e8cee4e428329a7668584ba76bf8de13 | 22.837 | 5.2.2 Pre-conditions | Good partnership and cooperation are established between the road supervision department and Mobile Operator#A in City#B. Requested by the supervision departments for the sensing service, the suitable base stations around/along a highway are selected, which enable Mobile Operator#A to constantly sense the road situation including moving objects (e.g. vehicles and pedestrians). The sensing signal emitted from the base station arrives at vehicles/pedestrians/objects on the road and is bounced (reflected) back to the transmitting base station. |
e8cee4e428329a7668584ba76bf8de13 | 22.837 | 5.2.3 Service Flows | Figure 5.2.3-1: Pedestrian/animal intrusion detection
1. Fei is a tourist, who is taking a taxi to enjoy the view around the highway in City #B. The base stations around/along the highway constantly sense the road situation. While the taxi is driving on the highway, Fei rolls down the window to take some pictures. Suddenly his mobile phone falls out the window.
2. Fei tells the driver to stop and cautiously gets out of the taxi. He crosses the highway and wants to find his mobile phone. Meanwhile, some animals (e.g. sheep and deer) from a farm near the highway approach the road. More and more surrounding vehicles are passing at very high speed. The pedestrian and animals are detected and closely tracked with sufficient accuracy in the sensing area of a base station, and then the 3GPP sensing data is transferred to the core network from the RAN and further processed into the sensing results in the core network.
3. The sensing results are exposed by the Mobile Operator #A to the road supervision departments and map provider. The map provider adds the position of the vulnerable pedestrian and animals into the HD dynamic maps and transmits warning messages to the vehicles approaching them. Alternatively, RSUs are connected to the traffic control centre for management and control purposes. RSUs transmit warning messages to the vehicles approaching them. The staff working for supervision departments immediately responds to the emergency, launching temporary traffic management, and rushes to the emergency site to fetch the mobile phone for Fei and drive the animals away from the highway.
4. Finally, Fei and animals leaves the highway safely. Potential road accident(s) caused by the pedestrian/animal intrusion are avoided. |
e8cee4e428329a7668584ba76bf8de13 | 22.837 | 5.2.4 Post-conditions | Thanks to the area-coverage, long-distance sensing capability of the base station (which provides a bird’s-eye-view for monitoring the highway environment) the precision and efficiency of highway management and safety supervision is improved. The network-based sensing can provide timely, continuous, accurate, and comprehensive sensing results, which is a reliable basis for highway safety services. |
e8cee4e428329a7668584ba76bf8de13 | 22.837 | 5.2.5 Existing features partly or fully covering the use case functionality | None. |
e8cee4e428329a7668584ba76bf8de13 | 22.837 | 5.2.6 Potential New Requirements needed to support the use case | [PR 5.2.6-1] The 5G system shall be able to support a base station to perform sensing.
[PR 5.2.6-2] The 5G system shall be able to support means to select suitable base station(s) to perform sensing, e.g. based on the base station’s location, sensing capability, and the sensing service information requested by trusted third party application.
[PR 5.2.6-3] The 5G system shall be able to support means to configure the sensing operation of a base station(e.g. authorization, sensing activation and/or deactivation, sensing duration, sensing accuracy, target sensing location area).
[PR 5.2.6-4] The 5G system shall be able to support means to enable a base station to transfer 3GPP sensing data to the core network.
[PR 5.2.6-5] The 5G system shall be able to support means to enable the core network to process 3GPP sensing data for obtaining sensing results.
[PR 5.2.6-6] Based on operator’s policy, the 5G system shall expose a suitable API to a trusted third party to provide the information regarding sensing results.
[PR 5.2.6-7] The 5G system shall be able to support charging data collection for the sensing services (e.g. considering service type, sensing accuracy, target area, duration) requested by a trusted third-party application.
[PR 5.2.6-8] Subject to operator’s policy, the 5G network may provide secure means for the operator to expose information on sensing service availability (e.g., if sensing service is available and the supported KPIs) in a desired sensing service area location to a trusted third-party.
[PR 5.2.6-9] The 5G system shall be able to support the following KPIs:
Table 5.2.6-1 Performance requirements of sensing results for pedestrian/animal intrusion detection
Scenario
Sensing service area
Confidence level [%]
Accuracy of positioning estimate by sensing (for a target confidence level)
Accuracy of velocity estimate by sensing (for a target confidence level)
Sensing resolution
Max sensing service latency[ms]
Refreshing rate [s]
Missed detection [%]
False alarm [%]
Horizontal
[m]
Vertical
[m]
Horizontal
[m/s]
Vertical
[m/s]
Range resolution
[m]
Velocity resolution (horizontal/ vertical)
[m/s x m/s]
Pedestrian/animal intrusion detection on a highway
Outdoor (Highway)
95
≤1
N/A
N/A
N/A
N/A
N/A
≤5000
≤ 0.1
≤5
≤5
NOTE: The terms in Table 5.2.6-1 are found in Section 3.1.
NOTE: In this use case base station is acting as sensing transmitter and/or sensing receiver. This is an example and other options can also be valid. |
e8cee4e428329a7668584ba76bf8de13 | 22.837 | 5.3 Use case on rainfall monitoring | |
e8cee4e428329a7668584ba76bf8de13 | 22.837 | 5.3.1 Description | Rainfall monitoring is a topic of great importance for several application contexts: hydraulic structure design, agriculture, weather forecasting, climate modelling, etc. At present, the most widely used measurement method is rain gauge.
Traditional rainfall monitoring use rain gauges, which are located at a particular location. Wide-area rainfall monitoring using traditional rain gauges would be costly. The base stations are deployed by the operators with radio cell planning that could cover a wider area. With base stations monitoring the rainfall, for example rain rate (mm/h), it could obtain a horizontally wider-area measurement.
Radio signals, as they propagate through the atmosphere, are reduced in intensity by constituents of the atmosphere. Oxygen and water vapor are the two major components which are responsible for the signal absorption. If it is a rainy day, an additional attenuation caused by rain further increases the propagation path loss. [7] The rain attenuation depends on the size and distribution of the water droplets, hence, by quantifying and modelling the base station signal measurements, we are able to know the rain rate.
The mmWave bands, such as 28GHz and 38GHz have been used to assess coverage, large-scale path loss, and fading and multipath effects [6]. Since the 28 GHz and 38 GHz bands are also licensed for wireless backhaul communications, these frequencies can be used for rainfall monitoring [7].
The granularity of the rainfall monitoring could be smaller than the traditional measurements. |
e8cee4e428329a7668584ba76bf8de13 | 22.837 | 5.3.2 Pre-conditions | Peter is a farmer who takes care of a big farm that grows different crops. Peter needs to monitor the rainfall of his farm to manage reasonable irrigation, drainage and fertilizer. When there is less rainfall, Peter can select reasonable irrigation plans to improve the farmland water content condition. When there is high rainfall, Peter should improve the drainage system and fertilize the crops to avoid crop losses. |
e8cee4e428329a7668584ba76bf8de13 | 22.837 | 5.3.3 Service Flows | 1) Peter has a subscription for the premium service of rainfall monitoring for a more granular location.
2) Peter is at daily working routine and wants to check the timely rainfall information from the weather application on his phone.
3) The RAN obtains the NR based 3GPP sensing data every hour and the 5G system processes the 3GPP sensing data to obtain sensing results and exposes the NR based sensing results to the weather application via the core network.
4) Based on the sensing results above, the application server obtains the rainfall information (i.e. rainfall and whether it is raining) associated with location information.
5) Peter obtains timely rainfall information from weather application on his phone. |
e8cee4e428329a7668584ba76bf8de13 | 22.837 | 5.3.4 Post-conditions | Peter could check the rainfall information at any time on his phone. Based on the timely rainfall information, Peter could plan the irrigation, drainage and fertilizer for the crops in his farm. |
e8cee4e428329a7668584ba76bf8de13 | 22.837 | 5.3.5 Existing feature partly or fully covering use case functionality | None. |
e8cee4e428329a7668584ba76bf8de13 | 22.837 | 5.3.6 Potential New Requirements needed to support the use case | [PR 5.3.6-1] The 5G network shall support collection of the NR based 3GPP sensing data from the base station.
[PR 5.3.6-2] Based on operator’s policy, the 5G system shall support mechanisms to process the 3GPP sensing data to derive the sensing results.
[PR 5.3.6-3] Based on operator’s policy, the 5G system shall provide mechanisms to expose NR based sensing results with sensing contextual information, e.g. location, to a trusted third-party application via the core network.
[PR 5.3.6-4] The 5G system shall support sensing services with KPIs as given in Table 5.3.6-1.
Table 5.3.6-1 Performance requirements of sensing results for rainfall monitoring
Scenario
Sensing service area
Confidence level [%]
Rainfall estimation accuracy
(for a target confidence level)
Accuracy of positioning estimate by sensing (for a target confidence level)
Accuracy of velocity estimate by sensing (for a target confidence level)
Sensing resolution
Max sensing service latency[ms]
Refreshing rate [s]
Missed detection [%]
False alarm [%]
Horizontal
[m]
Vertical
[m]
Horizontal
[m/s]
Vertical
[m/s]
Range resolution
[m]
Velocity resolution (horizontal/ vertical)
[m/s x m/s]
Rainfall monitoring
outdoor
95
[1mm/h]
NOTE 2
N/A
N/A
N/A
N/A
N/A
N/A
1 min
10min, application configurable
5
5
NOTE 1: The terms in Table 5.3.6-1 are found in Section 3.1.
NOTE 2: For rainfall rain rate >1 mm/h[39]. Rainfall estimation accuracy describes the closeness of the measured rainfall estimation to its true rainfall value.
NOTE: In this use case base station is acting as sensing transmitter and/or sensing receiver. This is an example and other options can also be valid. |
e8cee4e428329a7668584ba76bf8de13 | 22.837 | 5.4 Use Case on Transparent Sensing Use Case |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.