hash stringlengths 32 32 | doc_id stringlengths 5 12 | section stringlengths 5 1.47k | content stringlengths 0 6.67M |
|---|---|---|---|
ac78a8585cc1fb76fae88ca4aff4257c | 22.261 | 7.6 High data rate and low latency
| |
ac78a8585cc1fb76fae88ca4aff4257c | 22.261 | 7.6.1 AR/VR
| Audio-visual interaction is characterised by a human being interacting with the environment or people, or controlling a UE, and relying on audio-visual feedback. In the use cases like VR and interactive conversation the latency requirements include the latencies at the application layer (e.g. codecs), which could be sp... |
ac78a8585cc1fb76fae88ca4aff4257c | 22.261 | 7.7 KPIs for UE to network relaying in 5G system
| In several scenarios, it can be beneficial to relay communication between one UE and the network via one or more other UEs. The functional requirements related to relaying can be found in clause 6.9.2. Performance requirements for relaying in different scenarios can be found in table 7.7-1.
Table 7.7-1: Key Performanc... |
ac78a8585cc1fb76fae88ca4aff4257c | 22.261 | 7.8 KPIs for 5G Timing Resiliency
| The 5G system shall be able to support a holdover time capability with timing resiliency performance requirements defined in table 7.8-1.
Table 7.8-1: Timing resiliency performance requirements for 5G System
Use case
Holdover time (note 3)
Sync target
Sync accuracy
Service area
Mobility
Remarks
Power grid (5G ... |
ac78a8585cc1fb76fae88ca4aff4257c | 22.261 | 7.9 KPIs for ranging based services
| In several scenarios, it can be beneficial to determine the distance between two UEs and/or the direction of one UE from the other one via direct communication connection. The functional requirements related to ranging based services can be found in clause 6.37. Performance requirements for ranging based services in di... |
ac78a8585cc1fb76fae88ca4aff4257c | 22.261 | 7.10 KPIs for AI/ML model transfer in 5GS
| |
ac78a8585cc1fb76fae88ca4aff4257c | 22.261 | 7.10.1 KPI requirement for direct network connection
| The 5G system shall support split AI/ML inference between UE and Network Server/Application function with performance requirements as given in Table 7.10.1-1.
Table 7.10.1-1 KPI Table of split AI/ML inference between UE and Network Server/Application function
Uplink KPI
Downlink KPI
Remarks
Max allowed UL end-to-e... |
ac78a8585cc1fb76fae88ca4aff4257c | 22.261 | 7.10.2 KPI requirement for direct device connection
| The 5G system shall support split AI/ML inference between AI/ML endpoints by leveraging direct device connection with performance requirements as given in Table 7.10.2-1.
Table 7.10.2-1 KPI Table of Split AI/ML operation between AI/ML endpoints for AI inference by leveraging direct device connection
Max allowed end-t... |
ac78a8585cc1fb76fae88ca4aff4257c | 22.261 | 7.11 KPIs for tactile and multi-modal communication service
| The 5G system shall support tactile and multi-modal communication services with the following KPIs.
Table 7.11-1: Multi-modal communication service performance requirements
Use Cases
Characteristic parameter (KPI)
Influence quantity
Remarks
Max allowed end-to-end latency
Service bit rate: user-experienced data... |
ac78a8585cc1fb76fae88ca4aff4257c | 22.261 | 7.12 KPIs for direct device connection for Public Safety
| The functional requirements related to relaying of traffic between two Public Safety UEs using direct device connection via one or more ProSe UE-to-UE relay(s) can be found in clause 6.9.3. Performance requirements for relaying in different scenarios can be found in table 7.12-1.
Table 7.12-1: Key Performance for UE t... |
ac78a8585cc1fb76fae88ca4aff4257c | 22.261 | 7.13 KPIs for energy-related characteristics exposure
| The functional requirements related to exposing network energy-related characteristics can be found in clause 6.15a.5.
Exposing carbon equivalent emissions at subscriber level can rely on but does not imply any real-time collection, monitoring or exact subscriber-specific measurements or calculations. It can be provi... |
ac78a8585cc1fb76fae88ca4aff4257c | 22.261 | 8 Security
| |
ac78a8585cc1fb76fae88ca4aff4257c | 22.261 | 8.1 Description
| IoT introduces new UEs with different life cycles, including IoT devices with no user interface (e.g. embedded sensors), long life spans during which an IoT device can change ownership several times (e.g. consumer goods), and which cannot be pre-provisioned (e.g. consumer goods). These drive a need for secure mechanism... |
ac78a8585cc1fb76fae88ca4aff4257c | 22.261 | 8.2 General
| The 5G system shall support a secure mechanism to store cached data.
The 5G system shall support a secure mechanism to access a content caching application.
The 5G system shall support a secure mechanism to access a service or an application in an operator's Service Hosting Environment.
The 5G system shall enable su... |
ac78a8585cc1fb76fae88ca4aff4257c | 22.261 | 8.3 Authentication
| The 5G system shall support an efficient means to authenticate a user to an IoT device (e.g. biometrics).
The 5G system shall be able to support authentication over a non-3GPP access technology using 3GPP credentials.
The 5G system shall support operator-controlled alternative authentication methods (i.e. alternative... |
ac78a8585cc1fb76fae88ca4aff4257c | 22.261 | 8.4 Authorization
| The 5G system shall allow the operator to authorize an IoT device to use one or more 5G system features that are restricted to IoT devices.
The 5G system shall allow the operator to authorize /de-authorize UEs for using 5G LAN-type service.
NOTE: When a UE is de-authorized from using 5G LAN-type service, it is remove... |
ac78a8585cc1fb76fae88ca4aff4257c | 22.261 | 8.5 Identity management
| The 5G system shall provide a mechanism for an operator to allow access from a UE using a temporary identifier that hides its subscriber identity.
The 5G system shall provide a mechanism for an operator to allow access from a UE connected in an indirect network connection using a temporary identifier that hides its su... |
ac78a8585cc1fb76fae88ca4aff4257c | 22.261 | 8.6 Regulatory
| The 5G system shall support regional or national regulatory requirements for all supported access networks.
The 5G system shall support Lawful Interception, subject to regional or national regulatory requirements.
A 5G satellite access network connected to 5G core networks in multiple countries shall be able to meet ... |
ac78a8585cc1fb76fae88ca4aff4257c | 22.261 | 8.7 Fraud protection
| Subject to regional or national regulatory requirements, the 5G system shall support a secure mechanism for allowing an authorized entity to disable from normal operation of a UE reported as stolen.
Subject to regional or national regulatory requirements, the 5G system shall support a secure mechanism for allowing an ... |
ac78a8585cc1fb76fae88ca4aff4257c | 22.261 | 8.8 Resource efficiency
| The 5G system shall minimize security signalling overhead without compromising the security level of the 3GPP system.
The 5G system shall support an efficient secure mechanism to transmit the same data (e.g. service provisioning multiple sensors) to multiple UEs.
|
ac78a8585cc1fb76fae88ca4aff4257c | 22.261 | 8.9 Data security and privacy
| The 5G system shall support data integrity protection and confidentiality methods that serve URLLC, high data rates and energy constrained devices.
The 5G system shall support a mechanism to verify the integrity of a message as well as the authenticity of the sender of the message.
The 5G system shall support encryp... |
ac78a8585cc1fb76fae88ca4aff4257c | 22.261 | 8.10 5G Timing Resiliency
| The 5G system shall support a mechanism to verify authorization of a 3rd party application to use 5G timing resiliency.
The 5G system shall support a mechanism to monitor and verify authenticity of the timing source, where supported by the time source.
|
ac78a8585cc1fb76fae88ca4aff4257c | 22.261 | 9 Charging aspects
| 9.0 Introduction
This clause addresses the charging aspects of the different services/features described in the present document. Functional service requirements for the respective services/features can be found in the subclauses with the respective titles under clause 6.
|
ac78a8585cc1fb76fae88ca4aff4257c | 22.261 | 9.1 General
| The following set of requirements complement the requirements listed in 3GPP TS 22.115 [11]. The requirements apply for both home and roaming cases.
The 5G core network shall support collection of all charging information on either a network or a slice basis.
The 5G core network shall support collection of charging ... |
ac78a8585cc1fb76fae88ca4aff4257c | 22.261 | 9.2 5G LAN-type service
| A 5G core network shall support collection of charging information for a 5G LAN-type service based on resource usage (e.g. licensed or unlicensed spectrum, QoS, applications).
The 5G core network shall support collection of charging information for a 5G LAN-type service when a UE joins or leaves a specific private com... |
ac78a8585cc1fb76fae88ca4aff4257c | 22.261 | 9.3 5G Timing Resiliency
| The 5G system shall be able to collect charging information based on the timing source (e.g., the source in use, start and stop of source usage).
The 5G system shall be able to collect charging information per UE for use of a timing source (e.g., start/stop time and source used by a UE, timing source used by UE, holdo... |
ac78a8585cc1fb76fae88ca4aff4257c | 22.261 | 9.4 Satellite Access
| In a 5G system with satellite access, charging data records associated with satellite access(es) shall include the location of the associated UE(s) with satellite access.
NOTE: The precision of the location of the UE can be based on the capabilities of the UE or of the network.
A 5G system with satellite access suppo... |
ac78a8585cc1fb76fae88ca4aff4257c | 22.261 | 9.5 Energy efficiency as a Service Criteria
| Charging requirements for "Energy efficiency as a Service Criteria" can be found in clauses 6.15a2, 6.15a3 and 6.15a6 of this document.
|
ac78a8585cc1fb76fae88ca4aff4257c | 22.261 | 9.6 NG-RAN Sharing
| The 5G core network shall be able to support collection of charging information associated with a UE accessing a Shared NG-RAN using Indirect Network Sharing, which refers to the resource usage of hosting operator’s core network.
NOTE: When Shared NG-RAN is a shared satellite NG-RAN, the charging information can inclu... |
ac78a8585cc1fb76fae88ca4aff4257c | 22.261 | 9.12 5G wireless sensing service
| Charging requirements for "5G wireless sensing" can be found in clause 5.25 of 3GPP TS 22.137 [51].
9.13 Ambient power-enabled IoT
Charging requirements for "Ambient power-enabled IoT" can be found in clause 5.25 of 3GPP TS 22.369 [52].
9.14 Mobile Metaverse Services
Charging requirements for "Mobile Metaverse Se... |
ac78a8585cc1fb76fae88ca4aff4257c | 22.261 | 9.15 Traffic steering and switching over two 3GPP access networks
| Subject to HPLMN policy and network control, the 5G system shall be able to collect charging information related to traffic steering and/or switching of a DualSteer device’s user data across two 3GPP access networks.
NOTE: Charging information should be collected for both 3GPP access networks; in case the two 3GPP ac... |
4cadee5dc2d7ee9679f3455ce2627fca | 22.268 | 1 Scope
| This Technical Specification defines the stage one description of the Public Warning System (PWS) Requirements. Stage one is the set of requirements seen primarily from the users’ and service providers’ points of view.
The scope of this TS covers the core requirements for the PWS that are sufficient to provide a compl... |
4cadee5dc2d7ee9679f3455ce2627fca | 22.268 | 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 a... |
4cadee5dc2d7ee9679f3455ce2627fca | 22.268 | 3 Definitions and abbreviations
| |
4cadee5dc2d7ee9679f3455ce2627fca | 22.268 | 3.1 Definitions
| For the purposes of the present document, the terms and definitions given in TR 21.905 [5] and the following apply. A term defined in the present document takes precedence over the definition of the same term, if any, in TR 21.905 [5].
Commercial Mobile Alert System (aka, Wireless Emergency Alert): Public Warning Syst... |
4cadee5dc2d7ee9679f3455ce2627fca | 22.268 | 3.2 Abbreviations
| For the purposes of the present document, the abbreviations given in TR 21.905 [5] and the following apply. An abbreviation defined in the present document takes precedence over the definition of the same abbreviation, if any, in TR 21.905 [5]
CBC Cell Broadcast Centre
CBE Cell Broadcast Entity
CBS Cell Broadcast Se... |
4cadee5dc2d7ee9679f3455ce2627fca | 22.268 | 4 General PWS Requirements
| |
4cadee5dc2d7ee9679f3455ce2627fca | 22.268 | 4.1 Background
| Recently there has been an interest to ensure that the public has the capability to receive timely and accurate alerts, warnings and critical information regarding disasters and other emergencies irrespective of what communications technologies they use. As has been learned from disasters such as earthquakes, tsunamis,... |
4cadee5dc2d7ee9679f3455ce2627fca | 22.268 | 4.2 High level general requirements for Warning Notification delivery
| The following list gives the high level general requirements for Warning Notification delivery:
- PWS shall be able to broadcast Warning Notifications to multiple users simultaneously with no acknowledgement required.
- PWS shall be able to support concurrent broadcast of multiple Warning Notifications.
- Warning N... |
4cadee5dc2d7ee9679f3455ce2627fca | 22.268 | 4.3 Warning Notification Content
| PWS shall not modify or translate the Warning Notification content specified by the Warning Notification Provider.
It is expected that Warning Notifications would likely include the following five elements:
- Event Description
- Area Affected
- Recommended Action
- Expiration Time (with time zone)
- Sending ... |
4cadee5dc2d7ee9679f3455ce2627fca | 22.268 | 4.4 Granularity of the distribution
| Requirements for the granularity of the distribution of Warning Notifications include:
- Based on the geographical information indicated by the Warning Notification Provider, it shall be possible for the PLMN operators to define the Notification Area based on their network configuration of the area coverage such as di... |
4cadee5dc2d7ee9679f3455ce2627fca | 22.268 | 4.5 Support of Warning Notification Providers
| PLMN operators shall, at a minimum, be able to support the following functionalities through interaction with Warning Notification Providers:
- Activation of Warning Notification delivery
It shall be possible for multiple Warning Notifications to be activated concurrently from one or more Warning Notification Provid... |
4cadee5dc2d7ee9679f3455ce2627fca | 22.268 | 4.6 PWS-UE Requirements
| |
4cadee5dc2d7ee9679f3455ce2627fca | 22.268 | 4.6.1 General Requirements
| PWS-UEs shall only be required to receive and present Warning Notifications in languages as presented by the Warning Notification Provider. Regional/regulatory requirements may require the Warning Notifications to be broadcast in multiple languages.
There shall be no requirement for language translation in the operato... |
4cadee5dc2d7ee9679f3455ce2627fca | 22.268 | 4.6.2 Support of non-Warning Notification capable UEs
| Support of non-Warning Notification capable UEs is subject to regulatory requirements and/or operator's policy.
|
4cadee5dc2d7ee9679f3455ce2627fca | 22.268 | 4.6.3 Battery Life of PWS-UE
| Battery life of the PWS-UE shall not be significantly reduced by PWS.
|
4cadee5dc2d7ee9679f3455ce2627fca | 22.268 | 4.6.4 Enabling and disabling of Warning Notifications
| The PWS-UE shall be configured to receive all Warning Notifications.
It shall be possible for users to disable (e.g., opt-out) presentation of some or all of the Warning Notifications, subject to regulatory requirements and/or operator policy. The user shall be able to select PWS-UE enabling/disabling options via the ... |
4cadee5dc2d7ee9679f3455ce2627fca | 22.268 | 4.7 Roaming Requirements
| It shall be possible for PWS-UEs that are enabled for Warning Notifications in the HPLMN to receive Warning Notifications from the VPLMN supporting PWS when roaming.
A PWS-UE that does not support the PWS requirements of the VPLMN’s PWS service may not receive Warning Notifications from that VPLMN.
Note: See sectio... |
4cadee5dc2d7ee9679f3455ce2627fca | 22.268 | 4.8 Security Requirements
| Security requirements are as follows:
- PWS shall only broadcast Warning Notifications that come from an authenticated authorized source.
The following requirements only apply when not roaming internationally:
- When required by regional or national regulations, the integrity of the Warning Notification shall be pr... |
4cadee5dc2d7ee9679f3455ce2627fca | 22.268 | 4.9 Regulatory Requirements
| The PWS offered by a PLMN may be subject to PWS regional regulatory requirements and thus, the PWS offered may differ from PLMN to PLMN as well as from region to region within a PLMN.
|
4cadee5dc2d7ee9679f3455ce2627fca | 22.268 | 5 Earthquake and Tsunami Warning System
| |
4cadee5dc2d7ee9679f3455ce2627fca | 22.268 | 5.1 Background
| Warning Notifications are expected to be delivered to the users while satisfying the following requirements:
- Quick Warning Notification delivery after the occurrence of Earthquake or Tsunami.
Earthquake and Tsunami propagate very fast. The duration time between the actual occurrence of the disaster and its arrival... |
4cadee5dc2d7ee9679f3455ce2627fca | 22.268 | 5.2 Duration of delivery time
| Duration of the delivery time for PLMN operators is the time from the receipt of the Warning Notification by the PLMN operator, i.e. the edge of the 3GPP network, to the time that the Warning Notification is successfully delivered to the UEs.
Provisioning of delivery of Primary and Secondary Notification may be requir... |
4cadee5dc2d7ee9679f3455ce2627fca | 22.268 | 5.3 Information element and volume
| The following are the requirements from the perspective of information element and amount of data.
Both Primary and Secondary Notification shall:
- support at least 2 types of emergency events, which are Earthquake and Tsunami;
- be able to indicate the preferred UE behaviours when receiving Warning Notification, (... |
4cadee5dc2d7ee9679f3455ce2627fca | 22.268 | 5.4 Priority
| Requirements from the perspective of priority are as follows:
- Primary Notification has higher priority than Secondary Notification.
- Notifications shall be able to be sequenced by the PLMN according to priority of notification in case that Primary Notification and Secondary Notification should exist at the same ... |
4cadee5dc2d7ee9679f3455ce2627fca | 22.268 | 5.5 Roaming users
| Upon receiving Primary Notification which includes small amount of data to indicate the imminent occurrence of an Earthquake and/or Tsunami, the UE shall display the Warning Notification in a way that is easy to understand by the user, such as an icon or picture.
Note: It is expected that that the Warning Notification... |
4cadee5dc2d7ee9679f3455ce2627fca | 22.268 | 5.6 Additional PWS Requirements Specific to ETWS
| Subject to local/regional regulatory requirements, in addition to ETWS Primary and Secondary Notifications, ETWS shall be able to support broadcasting Warning Notification Area(s). This requirement applies to Satellite E-UTRAN and Satellite NG-RAN.
Subject to local/regional regulatory requirements, an ETWS-capable UE ... |
4cadee5dc2d7ee9679f3455ce2627fca | 22.268 | 6 CMAS Specific Requirements
| |
4cadee5dc2d7ee9679f3455ce2627fca | 22.268 | 6.1 Introduction to CMAS
| The Warning Alert and Response Network (WARN) Act was passed by the United States Congress in September 2006 and was signed into law on October 13, 2006, known then as CMAS. CMAS was later renamed as Wireless Emergency Alert (WEA).
The Federal Communication Commission (FCC) released several Report and Order rulings fo... |
4cadee5dc2d7ee9679f3455ce2627fca | 22.268 | 6.2 Additional PWS Requirements Specific to CMAS
| In addition to the General Requirements specified in Clause 4, the following requirements are specified for the deployment of CMAS. These CMAS specific requirements are based on the FCC Report and Orders listed in clause 6.1 and further specified in [4].
Warning Notifications shall support up to 360 characters of GSM... |
4cadee5dc2d7ee9679f3455ce2627fca | 22.268 | 7 EU-ALERT Specific Requirements
| |
4cadee5dc2d7ee9679f3455ce2627fca | 22.268 | 7.1 Introduction to EU-ALERT
| The generic name for the European Public Warning System is EU-ALERT. The letters EU will be replaced by characters identifying a particular country (e.g. NL-ALERT signifying the Netherlands, UK-ALERT signifying the United Kingdom). Such a strategy will allow each country to configure their own Public Warning System to ... |
4cadee5dc2d7ee9679f3455ce2627fca | 22.268 | 7.2 Additional PWS Requirements Specific to EU-ALERT
| In addition to the General Requirements specified in Clause 4, the following requirements are specified for the deployment of EU-ALERT. These EU-ALERT specific requirements are further specified in ETSI TS 102 900 [6].
EU-ALERT shall support three types of Warning Notifications: Alert messages to warn citizens of an i... |
4cadee5dc2d7ee9679f3455ce2627fca | 22.268 | 8 Korean Public Alert System specific Requirements
| |
4cadee5dc2d7ee9679f3455ce2627fca | 22.268 | 8.1 Introduction to Korean Public Alert System
| Telecommunications Technology Association (TTA) has specified a Korean Public Alert System (KPAS) which is based on PWS in [7]. That specification includes the support of Korean Public Alert System (KPAS) messages via the LTE Warning Message Delivery functionality. The Korean Public Alert System (KPAS) specification [7... |
4cadee5dc2d7ee9679f3455ce2627fca | 22.268 | 8.2 Additional PWS Requirements Specific to Korean Public Alert System (KPAS)
| In addition to the General Requirements specified in Clause 4, the following requirements are specified for the Korean Public Alert System (KPAS) [7]:
- Two classes of Warning Notification shall be supported; class 0 & class 1.
- The classes are differentiated per opt-out function. Class 0 shall have no opt-out and c... |
4cadee5dc2d7ee9679f3455ce2627fca | 22.268 | 9 Enhancements of Public Warning System (ePWS)
| |
4cadee5dc2d7ee9679f3455ce2627fca | 22.268 | 9.1 Service description
| Requirements specified in the clause 9 do not apply for US WEA and Japan ETWS.
Enhancements of Public Warning System (ePWS) define behaviours for UEs with no user interface or with a user interface that is incapable of displaying text-based Warning Notifications when receiving a Warning Notification.
In addition, enh... |
4cadee5dc2d7ee9679f3455ce2627fca | 22.268 | 9.2 General Requirements
| 9.2.1 ePWS Requirements
ePWS-UEs shall only be required to receive and present Warning Notifications in languages as presented by the Warning Notification Provider. Regional/regulatory requirements may require the Warning Notifications to be broadcast in multiple languages.
There shall be no requirement for language ... |
4cadee5dc2d7ee9679f3455ce2627fca | 22.268 | 9.2.2 Battery Life of ePWS-UE
| Battery life of the ePWS-UE shall not be significantly reduced by ePWS.
|
4cadee5dc2d7ee9679f3455ce2627fca | 22.268 | 9.2.3 Enabling and disabling of Warning Notifications
| The ePWS-UE shall be configured to receive all Warning Notifications.
It shall be possible for users to disable (e.g., opt-out) presentation of some or all of the Warning Notifications, subject to regulatory requirements and/or operator policy. The user shall be able to select ePWS-UE enabling/disabling options via th... |
4cadee5dc2d7ee9679f3455ce2627fca | 22.268 | 9.3 Requirements for 3GPP system supporting ePWS-UEs
| The 3GPP system shall allow the content of a Warning Notification to include information that can be mapped to an event or a disaster and is identifiable by the ePWS-UEs.
NOTE: The information included in the content of a Warning Notification may be an identifier of an event or a disaster.
|
4cadee5dc2d7ee9679f3455ce2627fca | 22.268 | 9.4 Requirements for ePWS-UE incapable of displaying text based Warning Notification
| |
4cadee5dc2d7ee9679f3455ce2627fca | 22.268 | 9.4.1 Requirements for ePWS-UE with no user interface
| ePWS-UEs with no user interface shall be able to receive a Warning Notification broadcast from the 3GPP network.
Subject to the intended function of the ePWS-UE (e.g. IoT) which has no user interface and regional regulatory requirements, the ePWS-UE may either:
1. Ignore Warning Notification; or
2. Take actions cons... |
4cadee5dc2d7ee9679f3455ce2627fca | 22.268 | 9.4.2 Requirements for ePWS-UE with a user interface incapable of displaying text based Warning Notification
| The ePWS-UE with a user interface that is not capable of displaying a text-based content shall be able to support the reception of a Warning Notification broadcast from the 3GPP network and shall be able to support the extraction of the information on the type of a notified event or disaster from the received Warning N... |
4cadee5dc2d7ee9679f3455ce2627fca | 22.268 | 9.5 Requirements for the improvement of understanding the Warning Notification
| The ePWS-UE with a user interface providing accessibility extensions to mobile users with disabilities shall be able to support the reception of a Warning Notification broadcast from the 3GPP network.
The ePWS-UE with a user interface providing accessibility extensions to mobile users with disabilities shall be able t... |
4cadee5dc2d7ee9679f3455ce2627fca | 22.268 | 10 Relay of Warning Notification
| |
4cadee5dc2d7ee9679f3455ce2627fca | 22.268 | 10.1 Service description
| Requirements specified in the clause 10 do not apply for US WEA and Japan ETWS.
3GPP system specified the relay functionality that is useful to extend the coverage supported by 3GPP system. With the relay functionality, PWS-UEs and ePWS-UEs that play the role of a relay UE or a remote UE conform to behaviours specifie... |
4cadee5dc2d7ee9679f3455ce2627fca | 22.268 | 10.2 Requirements for the relay functionality
| A remote ePWS-UE and a remote PWS-UE shall be able to support the reception of a Warning Notification that is transmitted from an UE that supports the relay functionality.
A remote ePWS-UE and a remote PWS-UE shall be able to automatically suppress duplicated notifications. A duplicate is a repetition of a same notifi... |
4cadee5dc2d7ee9679f3455ce2627fca | 22.268 | 11 Chinese Public Alert System Specific Requirements
| |
4cadee5dc2d7ee9679f3455ce2627fca | 22.268 | 11.1 Introduction to Chinese Public Alert System (CPAS)
| Chinese Public Alert System (CPAS), specified by China Communications Standards Association (CCSA) supports CPAS message delivery via NG-RAN.
|
4cadee5dc2d7ee9679f3455ce2627fca | 22.268 | 11.2 Additional PWS Requirements Specific to CPAS
| In addition to the General Requirements specified in Clause 4, the following requirements are specified for CPAS:
- CPAS enabled UE shall identify specific CPAS types of Warning Notification when it is located in the CPAS service area.
NOTE：The description of Warning Notification types is defined by China Communicati... |
38055db1edaa9b8bf534dbc753cc4ba8 | 22.280 | 1 Scope
| The present document provides the service requirements that are common across two or more mission critical services, that is MCPTT, MCData and MCVideo. The mission critical services make use of capabilities included in Group Communications System Enablers and Proximity Services, with additional requirements specific to... |
38055db1edaa9b8bf534dbc753cc4ba8 | 22.280 | 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.
-... |
38055db1edaa9b8bf534dbc753cc4ba8 | 22.280 | 3 Definitions and abbreviations
| |
38055db1edaa9b8bf534dbc753cc4ba8 | 22.280 | 3.1 Definitions
| For the purposes of the present document, the terms and definitions given in 3GPP TR 21.905 [4] 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 [4].
Affiliated MCX Service Group Member: An MCX Service Group Member who has ... |
38055db1edaa9b8bf534dbc753cc4ba8 | 22.280 | 3.2 Abbreviations
| For the purposes of the present document, the abbreviations given in 3GPP TR 21.905 [4] 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 [4].
MCCoRe Mission Critical Services Common Requirements
MCData Mis... |
38055db1edaa9b8bf534dbc753cc4ba8 | 22.280 | 4 Overview
| |
38055db1edaa9b8bf534dbc753cc4ba8 | 22.280 | 4.1 Rationale for MCCoRe
| Further development of mission critical services beyond Mission Critical Push To Talk (MCPTT), such as Mission Critical Video (MCVideo) and Mission Critical Data (MCData), created an opportunity to re-use base functionality documented in the Stage 1 requirements for MCPTT. For example, the ability to communicate missio... |
38055db1edaa9b8bf534dbc753cc4ba8 | 22.280 | 4.2 MCCoRe creation process
| The creation of 3GPP TS 22.280 followed a thorough analysis by mission critical application stakeholders of all the requirements in 3GPP TS 22.179, TR 22.879, and TR 22.880. Each set of requirements was evaluated, requirement-by-requirement, to determine if any one requirement was applicable to another service (MCPTT, ... |
38055db1edaa9b8bf534dbc753cc4ba8 | 22.280 | 5.1.1 General aspects
| [R-5.1.1-001] The MCX Service shall allow an MCX User utilizing one or more MCX UE(s), concurrently, to sign-in and receive service on each of the MCX UE(s).
[R-5.1.1-002] The MCX Service shall provide a mechanism by which an MCX UE makes a MCX Service group transmission to any MCX Service Group(s) for which the curre... |
38055db1edaa9b8bf534dbc753cc4ba8 | 22.280 | 5.1.2 Group/status information
| [R-5.1.2-001] The MCX Service shall provide a mechanism by which an MCX Service UE determines in which of the MCX Service Groups for which it is authorized there is an on-going MCX Service Group Communication.
[R-5.1.2-002] The MCX Service shall provide a mechanism by which an authorized MCX User determines in which M... |
38055db1edaa9b8bf534dbc753cc4ba8 | 22.280 | 5.1.3 Group configuration
| [R-5.1.3-001] The MCX Service shall allow the MCX Service Administrator to restrict who can be a member of specific MCX Service Groups, so that those MCX Service Groups shall be inaccessible to other users, including dispatchers or supervisors.
[R-5.1.3-002] The MCX Service shall enable a properly provisioned and auth... |
38055db1edaa9b8bf534dbc753cc4ba8 | 22.280 | 5.1.4 Identification
| [R-5.1.4-001] The MCX Service shall support identifiers using character sets for international languages specified via configuration.
|
38055db1edaa9b8bf534dbc753cc4ba8 | 22.280 | 5.1.5 Membership/affiliation
| [R-5.1.5-001] The MCX Service shall provide a mechanism by which an MCX User determines the currently defined MCX Service Groups for which the MCX User is authorized.
[R-5.1.5-002] The MCX Service shall provide a mechanism by which an MCX UE determines the currently defined MCX Service Groups for which it is authorize... |
38055db1edaa9b8bf534dbc753cc4ba8 | 22.280 | 5.1.6 Group Communication administration
| [R-5.1.6-001] The MCX Service shall provide a mechanism for an MCX Service Administrator to configure the maximum duration for MCX Service Group Communications for MCX Users within their authority.
|
38055db1edaa9b8bf534dbc753cc4ba8 | 22.280 | 5.1.7 Prioritization
| [R-5.1.7-001] The MCX Service shall provide a mechanism to organize MCX Service Groups into a hierarchy(ies).
[R-5.1.7-002] The MCX Service shall provide a mechanism to prioritize MCX Service Group Communications based on the priorities associated with elements of the communication (e.g., service type, requesting iden... |
38055db1edaa9b8bf534dbc753cc4ba8 | 22.280 | 5.1.8 Charging requirements for MCX Service
| [R-5.1.8-001] The MCX Service shall support charging for MCX Service Group Communications.
[R-5.1.8-002] Void
[R-5.1.8-003] The MCX Service shall support time-of-day sensitive charging based on actual resource utilization, provided QoS and provided priority.
[R-5.1.8-004] The MCX Service shall generate charging dat... |
38055db1edaa9b8bf534dbc753cc4ba8 | 22.280 | 5.1.9 MCX Service Emergency Alert triggered by Location
| [R-5.1.9-001] The MCX Service shall provide a mechanism for an MCX Service Emergency Alert to be triggered when an MCX UE moves into a predefined area.
[R-5.1.9-002] The MCX Service shall provide a mechanism for an MCX Service Emergency Alert to be cancelled when the MCX UE moves out of a predefined area or to remain ... |
38055db1edaa9b8bf534dbc753cc4ba8 | 22.280 | 5.2 Broadcast Group
|
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.