Add marked Rel-20 conversions

marked/Rel-20/22_series/22153/raw.md

@@ -0,0 +1,1198 @@
+
+
+
+
+
+
+# Contents
+
+|                                                                      |    |
+|----------------------------------------------------------------------|----|
+| Foreword                                                             | 6  |
+| Introduction                                                         | 6  |
+| 1 Scope                                                              | 7  |
+| 2 References                                                         | 7  |
+| 3 Definitions and abbreviations                                      | 7  |
+| 3.1 Definitions                                                      | 7  |
+| 3.2 Abbreviations                                                    | 8  |
+| 4 General description                                                | 8  |
+| 5 High level requirements                                            | 9  |
+| 5.1 General                                                          | 9  |
+| 5.2 Priority session treatment in originating network                | 10 |
+| 5.3 Priority session progression                                     | 10 |
+| 5.4 Priority session treatment in terminating network                | 10 |
+| 5.4a Priority Data Bearer Service                                    | 11 |
+| 5.5 Priority levels                                                  | 11 |
+| 5.6 Invocation on demand                                             | 11 |
+| 5.7 Multimedia priority service code/identifier                      | 11 |
+| 5.8 Roaming                                                          | 12 |
+| 5.8.1 Roaming within the home country                                | 12 |
+| 5.8.2 Roaming outside the home country                               | 12 |
+| 5.9 Handover                                                         | 12 |
+| 5.10 Interworking with CS domain                                     | 12 |
+| 5.10.1 Mobile origination in the CS domain -> MPS mobile termination | 12 |
+| 5.10.2 MPS mobile origination -> mobile termination to the CS domain | 12 |
+| 5.10.3 CS Fallback from LTE                                          | 13 |
+| 5.10a Fallback in 5GS                                                | 13 |
+| 5.11 Network Management Functions                                    | 13 |
+| 5.12 Policy Control                                                  | 13 |
+| 5.13 Priority before service invocation                              | 13 |
+| 5.13.1 Overview of priority before service invocation                | 13 |
+| 5.13.2 Requirement for priority before service invocation            | 14 |
+| 5.14 Recovery/Restoration                                            | 14 |
+| 5.15 Quality of Service (QoS)                                        | 14 |
+| 5.16 Inter-network aspects                                           | 14 |
+| 5.17 Interactions with supplementary services                        | 15 |
+| 5.18 3GPP and non-3GPP accesses                                      | 15 |
+| 6 MMI aspects                                                        | 15 |
+| 7 Security and privacy                                               | 15 |
+| 7.1 General                                                          | 15 |
+| 7.2 Access Control                                                   | 16 |
+| 7.3 Integrity                                                        | 16 |
+| 7.4 Confidentiality/Privacy                                          | 16 |
+| 7.5 Use of Encryption                                                | 16 |
+| 7.6 Attestation of Authorized MPS Priority                           | 16 |
+| 8 Charging aspects                                                   | 16 |
+| 9 Service specific aspects                                           | 17 |
+| 9.1 MPS for MMTEL voice                                              | 17 |
+| 9.1.1 General                                                        | 17 |
+| 9.1.2 Invocation and revocation                                      | 17 |
+| 9.1.2.1 Invocation                                                   | 17 |
+| 9.1.2.2 Revocation                                                   | 18 |
+| 9.1.3 Authentication and authorization                               | 18 |
+
+|                                       |                                           |    |
+|---------------------------------------|-------------------------------------------|----|
+| 9.1.4                                 | Signalling                                | 19 |
+| 9.1.5                                 | Media                                     | 19 |
+| 9.2                                   | MPS for MMTEL video                       | 19 |
+| 9.2.1                                 | General                                   | 19 |
+| 9.2.2                                 | Invocation and revocation                 | 20 |
+| 9.2.2.1                               | Invocation                                | 20 |
+| 9.2.2.2                               | Revocation                                | 21 |
+| 9.2.3                                 | Authentication and authorization          | 21 |
+| 9.2.4                                 | Signalling                                | 21 |
+| 9.2.5                                 | Media                                     | 22 |
+| 9.3                                   | MPS for DTS                               | 22 |
+| 9.3.1                                 | General                                   | 22 |
+| 9.3.2                                 | Invocation and revocation                 | 23 |
+| 9.3.2.1                               | Invocation                                | 23 |
+| 9.3.2.2                               | Revocation                                | 24 |
+| 9.3.3                                 | Authentication and authorization          | 25 |
+| 9.3.4                                 | Signalling                                | 25 |
+| 9.3.5                                 | Media                                     | 25 |
+| 9.3.6                                 | QoS                                       | 26 |
+| 9.3.7                                 | Security                                  | 26 |
+| 9.4                                   | MPS for Messaging Services                | 26 |
+| 9.4.1                                 | General                                   | 26 |
+| 9.4.2                                 | Invocation and revocation                 | 26 |
+| 9.4.2.1                               | Invocation                                | 26 |
+| 9.4.2.2                               | Revocation                                | 27 |
+| 9.4.3                                 | Authentication and authorization          | 28 |
+| 9.4.4                                 | Signalling                                | 28 |
+| 9.4.5                                 | Message origination and termination       | 29 |
+| 9.4.5.1                               | IMS Messaging                             | 29 |
+| 9.4.5.2                               | SMS and MMS                               | 29 |
+| 9.4.5.3                               | MSGin5G                                   | 29 |
+| 9.4.8                                 | Security                                  | 29 |
+| 10                                    | Non-3GPP access                           | 30 |
+| 10.1                                  | MPS when access to the EPC/5GC is WLAN    | 30 |
+| 10.1.1                                | MPS for MMTEL voice and video             | 30 |
+| 10.1.1.1                              | General                                   | 30 |
+| 10.1.1.2                              | Authentication and authorization          | 30 |
+| 10.1.1.3                              | WLAN Interworking                         | 30 |
+| 10.1.2                                | MPS for DTS                               | 30 |
+| 10.1.2.1                              | General                                   | 30 |
+| 10.1.2.2                              | Authentication and authorization          | 31 |
+| 10.1.2.3                              | WLAN interworking                         | 31 |
+| 10.1.3                                | Void                                      | 31 |
+| 10.1.4                                | MPS for Messaging services                | 31 |
+| 10.1.4.1                              | General                                   | 31 |
+| 10.1.4.2                              | Authentication and authorization          | 31 |
+| 10.1.4.3                              | WLAN interworking                         | 31 |
+| 11                                    | MPS support in 3GPP system with satellite | 32 |
+| 11.1                                  | MPS for MMTEL voice and video             | 32 |
+| 11.1.1                                | General                                   | 32 |
+| 11.1.2                                | Service continuity                        | 32 |
+| 11.2                                  | MPS for DTS                               | 32 |
+| 11.2.1                                | General                                   | 32 |
+| 11.2.2                                | Service continuity                        | 32 |
+| 11.3                                  | MPS for Messaging services                | 32 |
+| 11.3.1                                | General                                   | 32 |
+| 11.3.2                                | Service continuity                        | 32 |
+| Annex A (informative): Change history |                                           | 33 |
+
+---
+
+## Foreword
+
+This Technical Specification has been produced by the 3<sup>rd</sup> Generation Partnership Project (3GPP).
+
+The contents of the present document are subject to continuing work within the TSG and may change following formal TSG approval. Should the TSG modify the contents of the present document, it will be re-released by the TSG with an identifying change of release date and an increase in version number as follows:
+
+Version x.y.z
+
+where:
+
+- x the first digit:
+  - 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.
+
+---
+
+## Introduction
+
+The response to emergency situations (e.g., floods, hurricanes, earthquakes, terrorist attacks) depends on the communication capabilities of public networks. In most cases, emergency responders use private radio systems to aid in the logistics of providing critically needed restoration services. However, certain government and emergency management officials and other authorised users have to rely on public network services when the communication capability of the serving network may be impaired, for example due to congestion or partial network infrastructure outages, perhaps due to a direct or indirect result of the emergency situation.
+
+Multimedia Priority Service, supported by the 3GPP system set of services and features, is one element creating the ability to deliver calls or complete sessions of a high priority nature from mobile to mobile networks, mobile to fixed networks, and fixed to mobile networks.
+
+---
+
+# 1 Scope
+
+The present document specifies the service requirements for Multimedia Priority Service (MPS).
+
+The scope of this document is to specify those requirements of MPS necessary to provide an end-to-end service and to interwork with external networks where needed. Service interactions with external networks are considered within the scope of this document although these interactions may be specified in other standards.
+
+---
+
+# 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 TR 22.952: "Priority Service Guide".                                                   |
+| [3] | 3GPP TS 22.067: "enhanced Multi-Level Precedence and Pre-emption service (eMLPP); Stage 1". |
+| [4] | 3GPP TS 23.067: "enhanced Multi-Level Precedence and Pre-emption service (eMLPP); Stage 2". |
+| [5] | 3GPP TS 24.067: "enhanced Multi-Level Precedence and Pre-emption service (eMLPP); Stage 3". |
+| [6] | 3GPP TS 22.011: "Service accessibility".                                                    |
+| [7] | 3GPP TS 22.261: "Service requirements for next generation new services and markets".        |
+
+---
+
+# 3 Definitions and abbreviations
+
+## 3.1 Definitions
+
+For the purposes of the present document, the terms and definitions given in TR 21.905 [1] and the following apply. A term defined in the present document takes precedence over the definition of the same term, if any, in TR 21.905 [1].
+
+**MPS session:** A session for which priority treatment is applied for allocating and maintaining radio and network resources.
+
+**MPS-subscribed UE:** A UE having MPS subscription.
+
+**Priority Treatment:** Refers to mechanisms and features that increase the success rate for MPS session invocation, establishment and maintenance until release.
+
+**Service User:** An individual authorized to use MPS and who has been granted a user priority level assignment by a regional/national authority (i.e., an agency authorised to issue priority assignments), and has a subscription to a mobile network operator that supports the MPS feature.
+
+NOTE A Service User is not always restricted to a human user of the service (e.g., in the case of IoT, it could be a specialized application using MPS through machine interactions that may not directly involve a human Service User).
+
+## 3.2 Abbreviations
+
+For the purposes of the present document, the abbreviations given in TR 21.905 [1] and the following apply. An abbreviation defined in the present document takes precedence over the definition of the same abbreviation, if any, in TR 21.905 [1].
+
+|              |                                |
+|--------------|--------------------------------|
+| <b>DTS</b>   | Data Transport Service         |
+| <b>MMTEL</b> | Multimedia Telephony           |
+| <b>MPS</b>   | Multimedia Priority Service    |
+| <b>OTT</b>   | Over-The-Top                   |
+| <b>PIN</b>   | Personal Identification Number |
+| <b>VPN</b>   | Virtual Private Network        |
+
+---
+
+## 4 General description
+
+MPS is applicable in EPS and 5GS systems.
+
+MPS provides priority treatment to increase the probability of an authorized Service User's Voice, Video, Data and Messaging communication being successful. Some form of priority treatment is applied to the MPS invocation and session establishment, and continues to be applied until the MPS session is released. The priority treatment may be applied before the invocation if a greater probability of success in receiving, recognizing, and processing the invocation is needed.
+
+MPS allows qualified and authorized users to obtain priority access to the next available radio channel on a priority basis before other PLMN users, during situations when PLMN congestion is blocking session establishment attempts. In addition, MPS supports priority sessions on an "end-to-end" priority basis.
+
+MPS is intended to be utilised for Voice, Video, Messaging and Data bearer services, including the Data Transport Service, in the Packet-switched (PS) domain and the IP Multimedia Subsystem (IMS). It also involves priority transitioning of MPS service (e.g., Voice) to the CS domain when the network does not support the requested service in the PS domain. MPS sessions for Voice, Video, Data, and Messaging are based on providing priority treatment to the corresponding commercial services offered to the public.
+
+MPS is also intended to be utilized for IoT communications through machine interactions that may not directly involve a human Service User.
+
+MPS includes network functions that fall into the following broad categories:
+
+**Service Invocation:** The process to recognize and identify a request for an MPS session. An MPS Service Provider network recognizes an MPS invocation based on the presence of an MPS-unique identifier entered by the originating Service User in the service request received by the network from the UE, or based on the subscription profile of the originating UE, or as a regional/operator option the subscription profile of the terminating UE.
+
+NOTE: The option related to "subscription profile of the terminating UE" may not involve end-to-end priority because this option is based on providing priority only in the terminating network based on the terminating UE subscription profile.
+
+**Authorization:** The process to verify that a Service User is authorized for MPS. This includes capabilities to verify authorization to receive priority treatment in the radio access network and to access the MPS application service (MPS Voice, Video, Data, and Messaging).
+
+**End-to-End Priority Treatment:** The process of providing priority treatment in all parts of the path, from one endpoint to the other endpoint(s). End-to-end priority treatment includes priority treatment by all MPS capable networks involved in the MPS session path, the origination network and the termination network as well as any transit networks in between.
+
+**Invocation-to-Release Priority Treatment:** The process of providing priority treatment to all phases of a session, from invocation until release, including all steps in between.
+
+The combination of End-to-End Priority Treatment and Invocation-to-Release Priority Treatment includes both pre- and post-authorization treatment and includes the following aspects:
+
+- 1) Priority processing of the Service User's MPS invocation,
+- 2) Admission control and allocation of network resources (including bearer resources) in origination, termination, and transit networks, including handovers,
+- 3) Transport of signaling and media packets,
+- 4) Priority processing within EPS, 5GS and CN, and
+- 5) Processing of the Service User's release of an MPS service session.
+
+Network Interconnection and Protocol Interworking: A Service User's MPS invocation and session establishment will involve transport and processing, and the end-to-end signaling and media path may traverse multiple MPS Service Provider networks. These end-to-end cases include, but are not limited to:
+
+- 1) Voice, video, data and messaging services over EPS or 5GS, including signaling for call/session establishment and media;
+- 2) EPS/5GS interworking with the CS domain, including a) calls originated in the CS domain and terminated in EPS/5GS, and b) calls from EPS/5GS to the CS domain;
+- 3) CS Fallback from EPS, for one or both ends of call, with maintenance of existing PS domain MPS services, either in EPS or in a legacy system, e.g., the GPRS Core; and
+- 4) Access to MPS data, video, and messaging services not under IMS control.
+
+---
+
+# 5 High level requirements
+
+## 5.1 General
+
+The system shall provide preferential treatment based on the subscription for MPS for:
+
+- An authorized Service User using a UE with an MPS subscription,
+
+NOTE 1: The MPS subscription related information is associated with the UE's HPLMN subscription and is either stored in the UE and the HPLMN, or only in the HPLMN. In the case that the MPS subscription is stored in the UE, the UE's membership in a special access class as per TS 22.011 [6] is used for E-UTRAN access to the EPC and membership in Access Identity 1 as per TS 22.261 [7] is used for 5GS (NR and E-UTRA access to the 5GC). In the case where the MPS subscription is stored only in the HPLMN (5GC), the HPLMN (5GC) can provide MPS indication during the UE registration.
+
+- An authorized Service User using a UE that does not have an MPS subscription, and
+
+NOTE 2: In this case, the Service User's MPS subscription information (e.g., credentials) is not associated with the UE's HPLMN subscription. For example, the Service User borrows a UE that does not have an MPS subscription. .
+
+- An authorized IoT device with an MPS subscription.
+
+NOTE 3: The MPS subscription related information is associated with the IoT device's HPLMN subscription and is either stored in the IoT device and the HPLMN, or only in the HPLMN to allow invocation/revocation of MPS through machine interactions possibly without involving a human. .
+
+Upon invocation of MPS, the system shall provide preferential treatment for access and core network resources associated with the session (i.e., signalling and media bearer related resources within a domain and across domains), including, when applicable, priority treatment towards an enterprise network supporting MPS.
+
+NOTE 4: 'enterprise network' (mentioned above, and in other following sections) may be a 3GPP or non-3GPP network.
+
+A Service User is assigned a priority level by a regional/national authority i.e., agency authorised to issue priority levels. Upon MPS invocation the calling Service User's priority level is used to identify the priority to be used for the session being established.
+
+Pre-emption of active sessions shall be subject to regional/national regulatory requirements.
+
+Subject to regional/national regulatory policy, a PLMN should have the capability to retain public access as a fundamental function. Therefore, MPS traffic volumes should be limited (e.g. not to exceed a regional/national specified percentage of any concentrated network resource, such as eNodeB capacity), so as not to compromise this function.
+
+## 5.2 Priority session treatment in originating network
+
+When an MPS session is originated by a Service User, the session shall receive priority treatment (priority access to signalling and media bearer resources for voice, video, data, and messaging service) in the originating PLMN based on the originating Service User priority information (i.e., priority indication and priority level).
+
+When an MPS session is requested by a Service User and the originating network supporting session establishment cannot assign the necessary resources to the MPS session, the MPS session request shall be:
+
+- Queued,
+- Processed for the next available resource in accordance with the calling Service User's priority level and session initiation time.
+
+The network shall support the capability to inform the calling Service User about the status of the MPS session (e.g., tones or signalling messages can be used to indicate that the session request has been queued).
+
+If the queued MPS session times out, then normal session processing applies.
+
+## 5.3 Priority session progression
+
+For an MPS session, a Service User shall receive priority session treatment/progression through the PLMN(s). In case the MPS session traverses or terminates in other networks (e.g., the PSTN), the network providing priority session treatment/progression shall support the capability to indicate to the other network that this is an MPS session.
+
+NOTE: If there is no agreement on priority handling between networks, the priority does not carry across network boundaries.
+
+## 5.4 Priority session treatment in terminating network
+
+When a terminating network receives an incoming MPS session establishment attempt, the MPS session shall receive priority treatment (priority access to signalling and media bearer resources for voice, video, data, and messaging service) in the terminating PLMN, based on the originating Service User priority information. When requested, this includes MPS treatment towards an enterprise network supporting MPS.
+
+As an operator option, the terminating network may invoke priority treatment for an incoming session from a non-MPS subscriber to an MPS subscriber (see clause 4).
+
+When the terminating network supporting session establishment cannot assign the necessary resources to the MPS session, the MPS session request shall be:
+
+- Queued,
+- Processed for the next available resource in accordance with the Service User's priority level and session arrival time.
+
+The network shall support the capability to inform the calling Service User about the status of the MPS session (e.g., tones or signalling messages can be used to indicate that the session request has been queued).
+
+If the queued MPS session times out, then normal session processing applies.
+
+### 5.4a Priority Data Bearer Service
+
+The Priority Data Bearer Service provides MPS priority for data and video services not under IMS control.
+
+When a Service User invokes Priority Data Bearer Service for transport of any data packets to and from that Service User, the network should give priority in admission/upgrade of the Priority Data Bearer(s) and in packet data scheduling.
+
+in the event of congestion (for new sessions and upgrade to existing sessions), subject to regional/national regulatory policy. Specifically:
+
+- A Priority Data Bearer service session shall be given priority for admission/upgrade over non-Priority Data Bearer sessions during times of congestion;
+- Data packets belonging to a Priority Data Bearer service shall not be dropped before data packets belonging to a non-Priority Data Bearer service session, when the network is experiencing congestion, subject to the limitation imposed by public access. Priority Data Bearer session QoS, as required for the type of service invoked (e.g., packet delay), should be maintained throughout the activity of the data session.
+
+MPS for Data Transport Service (DTS) is a generic priority packet transport service that applies independently of the specific data application being used. In the case of EPS, MPS for DTS enables the prioritization of all traffic on the default bearer upon request. It may also apply to other bearers based on operator policy and regulatory rules. In the case of 5GS, MPS for DTS enables the prioritization of all traffic on the QoS Flow associated with the default QoS rule upon request. It may also apply to other QoS flows based on operator policy and regulatory rules. MPS for DTS is a specific example of Priority Data Bearer Service. MPS for DTS service specific requirements are described in clause 9.3.
+
+NOTE: MPS for streaming video can be provided as an Over The Top (OTT) service using the MPS for DTS service.
+
+## 5.5 Priority levels
+
+The Service User shall be assigned one of "n" user priority levels. The priority levels are defined with 1 being the highest priority level and "n" being the lowest priority level.
+
+The 3GPP network shall be able to support at least 5 user priority levels.
+
+Assignment of priority levels is a matter of regional/national and operator policy.
+
+In case of interconnecting networks that have different priority levels, mappings between priority levels should be established.
+
+## 5.6 Invocation on demand
+
+MPS priority shall be invoked only when requested by the Service User. However, certain priority treatments are provided prior to invocation as specified in Section 5.13.
+
+MPS is applied when idle resources required for an origination session request are not available.
+
+If idle resources are available when MPS is requested, the request shall be allowed to proceed as normal, but marked as an MPS request.
+
+An indication of an MPS session should be propagated towards the terminating network regardless of the availability of resources in the originating network.
+
+## 5.7 Multimedia priority service code/identifier
+
+MPS shall be requested by including an MPS code/identifier in the session origination request, or optionally, by using an MPS input string (e.g., an MPS public user identity).
+
+## 5.8 Roaming
+
+MPS shall be supported when the Service User is roaming and the visited network and home network support MPS, and roaming agreements are in place for MPS.
+
+### 5.8.1 Roaming within the home country
+
+The system shall support MPS when a UE with an MPS subscription is roaming within the home country and the visited and home network support MPS, and roaming agreements are in place for MPS.
+
+NOTE 1: Roaming within a home country is subject to national/regional rules and operator policy.
+
+NOTE 2: The MPS subscription related information associated with the UE's HPLMN subscriptionis used for roaming within the home country. Membership in a special access class as per TS 22.011 [6] is used for EUTRAN access to the EPC and membership in Access Identity 1 as per TS 22.261 [7] clause 6.22.2.2 is used for 5G (NR and E-UTRAN access to the 5GC).
+
+## 5.8.2 Roaming outside the home country
+
+The system shall support MPS when a UE with an MPS subscription is roaming outside of the home country and the visited and home network support MPS, and roaming agreements are in place for MPS.
+
+NOTE 1: Roaming outside a home country is subject to national/regional rules and operator policy.
+
+NOTE 2: The UE subscription in the home PLMN is configured for MPS with the visited PLMN outside the home country as specified in TS 22.261 [7] clause 6.22.2.2, for 5GS (E-UTRA and NR access to the 5GC).
+
+NOTE 3: The home PLMN can configure the UE to discover and select a network supporting MPS when roaming outside of the home country (e.g., the UE is configured to select a specific MPS capable visited PLMN when roaming in a country that may have multiple PLMNs where some are MPS capable and some are not MPS capable).
+
+## 5.9 Handover
+
+MPS shall be supported during and after the handover (i.e., sessions shall continue to get priority treatment in the network during and after the handover). Resource allocation for the session during handover shall receive priority treatment (priority access to signalling and media bearer resources for voice, video, and data) in the target cell based on the Service User priority information (i.e., priority indication and priority level).
+
+For handover of an MPS voice call to CS, only the active, or if all calls are on hold, only the most recently active voice call shall be transferred and receive the priority treatment in CS. Any remaining non-MPS voice sessions in PS may be released. Any remaining MPS sessions, e.g., MPS data, in PS shall not be released.
+
+## 5.10 Interworking with CS domain
+
+### 5.10.1 Mobile origination in the CS domain -> MPS mobile termination
+
+For a Priority Service voice call, as described in [2] and as specified in [3, 4, 5], originated by a Service User in the CS Domain, MPS shall support priority Mobile Termination of the session in the IMS. The priority information received from the CS domain shall be mapped and used in the IMS accordingly.
+
+### 5.10.2 MPS mobile origination -> mobile termination to the CS domain
+
+For an MPS voice session originated by a Service User in the IMS, MPS shall support priority delivery of the voice session to the serving CS Domain. The calling Service User priority level shall be sent to the CS Domain.
+
+### 5.10.3 CS Fallback from LTE
+
+Circuit Switched (CS) fallback from LTE needs to be given priority in the LTE system to support MPS voice in cells where voice is not supported in the PS domain. Priority treatment applies to both mobile originated calls and mobile terminated calls.
+
+When an MPS Service User in LTE originates a voice call intended to be supported in the CS domain, and when configured by the operator, the LTE system shall provide priority treatment in the signalling and resource allocations needed to support priority CS fallback.
+
+When a terminating LTE network receives indication of an incoming call to the CS domain, the LTE system shall provide priority treatment in the signalling and resource allocations needed to support priority CS fallback.
+
+### 5.10a Fallback in 5GS
+
+MPS voice calls need to be provided priority treatment following a voice fallback in 5GS when configured by the operator to fallback to another RAN type and/or core network type to support voice. The priority treatment applies to both mobile originated calls and mobile terminated calls. Non-voice PDU sessions that have priority in the 5GS prior to
+
+a voice fallback need to be given priority after the voice fallback. The priority treatment applies when the MPS non-voice PDU sessions move with the MPS voice PDU session and when MPS non-voice PDU sessions do not move with the MPS voice PDU session.
+
+When an MPS Service User in a 5GS originates an MPS voice call and when configured by the operator for voice fallback to another RAN type and/or core network type, the system shall provide priority treatment in the signalling and resource allocations to support the priority voice fallback.
+
+When a 5GS receives indication of a terminating MPS voice call and when configured by the operator for voice fallback to another RAN type and/or core network type, the system shall provide priority treatment in the signalling and resource allocations to support the priority voice fallback.
+
+When the 5GS initiates a voice fallback for an MPS call, the system shall provide priority treatment in the signalling and resource allocations needed to support non-voice priority PDU sessions, if any exist at the time of the voice fallback. The priority treatment shall apply whether the MPS non-voice PDU session moves with the MPS voice PDU session or not.
+
+## 5.11 Network Management Functions
+
+Based on regional/national requirements and network operator policy, an MPS session shall be exempted from network management controls up to the point where further exemption would cause network instability. Congestion controls, overload controls, load balancing, and load re-balancing shall not adversely impact MPS.
+
+## 5.12 Policy Control
+
+The 3GPP network shall be able to make and enforce policy decisions regarding relative treatment of MPS application services (Voice, Video, Data, and Messaging) for admission control subject to regional/national regulatory requirements and operator policy.
+
+The 3GPP network shall be able to make and enforce policy decisions regarding relative treatment of MPS application services traffic depending on the media type subject to regional/national regulatory requirements and operator policy (e.g., based on operator policy or regulation, Voice may have higher priority than Video or Data).
+
+## 5.13 Priority before service invocation
+
+### 5.13.1 Overview of priority before service invocation
+
+Providing priority treatment to MPS-subscribed UEs during attachment/registration for radio access and network connectivity before the MPS application service session invocation requests improves the probability of an MPS session request being successful. This involves providing priority treatment for the signalling during the UE attachment for radio access and network connectivity based on a subscription profile. Prior to accessing subscription related information in the network, subscription related information stored in the UE is used, e.g., membership in the special access class required to be reserved for MPS use as per 3GPP TS 22.011 [6], or the special Access Identity used for MPS as per 3GPP TS 22.261 [7]. Without such priority treatment, a Service User’s UE might fail to gain radio access network and CN connectivity which in turn means that there is no access to the MPS application services (Voice, Video, and Data). Priority treatment before MPS session request increases the probability of successful MPS session establishment and any associated process for the Service User authorization (e.g., credential collection).
+
+### 5.13.2 Requirement for priority before service invocation
+
+The 3GPP network shall be able to provide priority treatment to an MPS-subscribed UE before the MPS application service invocation (e.g., priority treatment for the default and IMS signalling bearers establishment based on a subscription profile).
+
+The 3GPP network shall be able to provide priority requests for access and attachment to the 3GPP network from an MPS-subscribed UE, including those procedures applied prior to and during the access of subscription related information (e.g., based on the UE membership in a special access class for MPS, or when allowed to operate with Access Identity 1 as per 3GPP TS 22.261 [7]).
+
+## 5.14 Recovery/Restoration
+
+The 3GPP system shall allow operational measures to expedite service recovery and restoration (i.e., service restoration after failure/unavailability). Should a disruption occur, MPS shall be re-provisioned, repaired, or restored to required service levels on a priority basis subject to regional/national regulatory requirements and operator policy.
+
+## 5.15 Quality of Service (QoS)
+
+In certain cases, the QoS characteristics (e.g., packet delay and packet loss) for an MPS session may be the same as the underlying communication service (e.g., voice, video, data or messaging) used to support the MPS session, with the MPS session being provided priority treatment subject to regional/national regulatory and operator policies. In other cases, there may be a need to request specific QoS characteristics for the MPS session (e.g., specific data communications as described in clause 5.4a, 9.3).
+
+The 3GPP network shall allow selection and/or configuration of QoS rule(s) appropriate for MPS Voice, Video, Data and Messaging.
+
+The 3GPP network shall allow enforcement of QoS rule(s) for MPS Voice, Video, Data, and Messaging.
+
+The system shall support means to retain MPS sessions invoked for Voice, Video, Data and Messaging during transient network degradation conditions and recovery (e.g., during short radio link interruption), and re-verify any recovered MPS session afterwards.
+
+## 5.16 Inter-network aspects
+
+The system shall allow MPS priorities to be signalled across interconnected networks.
+
+NOTE 1: Support of MPS services across networks is based on policy and agreements between the network operators.
+
+NOTE 2: Intermediate 3GPP networks not supporting MPS (e.g., transit networks between an originating network and terminating network) should allow MPS priorities to be signalled transparently, based on operator policy and agreements for MPS.
+
+The system shall support means to identify that an incoming voice, video, data or messaging service session from another network is an MPS session and to handle it with priority.
+
+The system shall support measures to verify policy and admit an incoming MPS session for Voice, Video, Data, or Messaging service received from another network with priority.
+
+## 5.17 Interactions with supplementary services
+
+Interactions with a supplementary service might occur during set-up or after establishment of an MPS call or session. A supplementary service is a service which modifies or supplements a basic telecommunication service (see definition in 3GPP TR 21.905 [1]).
+
+The system shall provide MPS priority for a supplementary service associated with an MPS call or session in progress when the supplementary service is associated with the Service User authorized for MPS.
+
+When a supplementary service (e.g., Communication Diversion) results in an established authorized MPS call or session being redirected or extended, MPS priority shall be provided for the redirected or extended call or session.
+
+When a supplementary service (e.g., Conference/Three-Party) is used to join an MPS priority call or session (e.g., to add parties to the established MPS call/session), MPS priority shall be retained on that leg when joined to the supplementary service.
+
+## 5.18 3GPP and non-3GPP accesses
+
+When a UE is using 3GPP RAT(s) as well as non-3GPP WLAN access technology, the 3GPP system will select the most appropriate 3GPP RAT or non-3GPP WLAN access technology for one or more services active on the UE. This subclause covers MPS handling when 3GPP RAT(s) and non-3GPP WLAN access technology are being used for one or more services active on a UE.
+
+The system shall support MPS based on operator policy when the UE is using 3GPP RAT(s) and non-3GPP WLAN and connected to the same EPC.
+
+The system shall support MPS based on operator policy when the UE is using 3GPP RAT(s) and non-3GPP WLAN and connected to the same 5GC.
+
+---
+
+# 6 MMI aspects
+
+In the case when MPS invocation is based on the presence of an MPS-specific service code entered by the originating Service User, this specific service code must be defined for the 3GPP network to recognize such an invocation.
+
+The 3GPP network supporting on-demand invocation of MPS shall recognize a service code indicating a request for MPS.
+
+NOTE: A Service User roaming within or outside the home country must use an MPS-specific service code recognized by the visited PLMN, to indicate a request for MPS based on the agreements between the home and visited PLMNs for MPS.
+
+The choice of an MPS-specific service code is a regional/national and operator matter.
+
+---
+
+# 7 Security and privacy
+
+## 7.1 General
+
+Operators support and use a wide range of security tools and capabilities to protect the 3GPP system and all supported application services. It is important that appropriate measures be taken to ensure that the use of these security capabilities does not negatively impact MPS.
+
+Use of security mechanisms (e.g., intrusion detection / prevention systems, deep packet inspection, and encryption) shall not interfere with priority treatment mechanisms supporting authorized MPS usage.
+
+## 7.2 Access Control
+
+Access to MPS shall be determined based on the subscriber's profile. A level of authorisation in addition to authorisation to use the IMS is required.
+
+Unauthorized access to MPS shall be prevented.
+
+## 7.3 Integrity
+
+The 3GPP system shall be capable of providing integrity protection to MPS signalling and media bearers for voice, video, data, and messaging service.
+
+## 7.4 Confidentiality/Privacy
+
+The 3GPP system shall be capable of providing confidentiality protection to MPS signalling and media bearers for voice, video, and data as appropriate.
+
+The 3GPP system shall be capable of maintaining anonymity of the originating Service User to the terminating party, if requested by the originating Service User.
+
+## 7.5 Use of Encryption
+
+If encryption is used on MPS communication, priority information shall be accessible to all network elements which have to understand and process that priority information.
+
+## 7.6 Attestation of Authorized MPS Priority
+
+A 3GPP system receiving a session with MPS priority from another network needs to verify that the session is authorized for MPS priority.
+
+The originating 3GPP system shall provide a means to securely attest to MPS authorization for the session.
+
+The 3GPP system shall provide a means to securely verify the attestation of MPS authorization received from the originating network for the session.
+
+---
+
+## 8 Charging aspects
+
+A network supporting MPS shall be capable of recording the following charging information, in addition to non-MPS information:
+
+- MPS invocation attempt and successful session set-up,
+- Session bearers (originations and/or terminations) on which MPS was used to gain access to resources,
+- Recording of MPS information, e.g., priority level.
+
+The system shall associate MPS related charging events with the MPS subscription.
+
+---
+
+## 9 Service specific aspects
+
+### 9.1 MPS for MMTEL voice
+
+#### 9.1.1 General
+
+MPS for MMTEL voice provides the Service User with priority voice communication sessions in periods of severe network congestion during which normal commercial voice service is degraded.
+
+The system shall support:
+
+- MPS for MMTEL voice and voice conference calls for an authorized Service User using a UE with a subscription for MPS,
+
+NOTE 1: The MPS subscription related information is associated with the UE's HPLMN subscription and is either stored in the UE and the HPLMN, or only in the HPLMN. In the case that the MPS subscription is stored in the UE, the UE's membership in a special access class as per TS 22.011 [6] is used for EUTRAN access to the EPC and membership in Access Identity 1 as per TS 22.261 [7] is used for 5G (NR and E-UTRAN access to the 5GC). In the case where the MPS subscription is stored only in the HPLMN (5GC), the HPLMN (5GC) can provide MPS indication during the UE registration.
+
+- MPS for MMTEL voice and voice conference calls for an authorized Service User using a UE that does not have an MPS subscription, and
+
+NOTE 2: In this case, the Service User's MPS subscription information (e.g., credentials) is not associated with the UE's HPLMN subscription. For example, the Service User borrows a UE that does not have an MPS subscription.
+
+- MPS for all participants of an authorized MMTEL voice conference call.
+
+NOTE 3: MPS for all participants of an MMTEL voice conference call allows a Service User (i.e., the host) to establish an MMTEL voice conference with MPS for all participants, or upgrade an ongoing MMTEL voice conference to MPS for all participants regardless of their subscription to MPS.
+
+#### 9.1.2 Invocation and revocation
+
+##### 9.1.2.1 Invocation
+
+A Service User, using a UE with an MPS subscription, can invoke MPS to request priority for an MMTEL voice/conference call, e.g., when the normal MMTEL call cannot be established, or to upgrade an already established normal MMTEL call to MPS.
+
+The system shall support means for a Service User using a UE with an MPS subscription to:
+
+- initiate MPS for an MMTEL voice call or an MPS MMTEL voice conference call, or
+- request upgrade of an established MMTEL voice call, or an established MMTEL voice conference call to MPS.
+
+NOTE 1: MPS invocation using a UE with an MPS subscription is done using a predetermined method (e.g., by the Service User inclusion of an MPS-unique identifier or feature code as part of the request to establish an MPS for MMTEL voice call).
+
+A Service User, using a UE with an MPS subscription, can invoke MPS to request priority for an MMTEL voice call or conference call during roaming, e.g., when the normal MMTEL voice/conference call cannot be established, or to upgrade an already established normal MMTEL call to MPS.
+
+The system shall support means for a Service User using a UE with an MPS subscription to:
+
+- initiate MPS for an MMTEL voice call, or an MPS MMTEL voice conference call when roaming within the home country and outside the home country, or
+- requests upgrade of an established MMTEL voice call, or an established MMTEL voice conference call to MPS when roaming within the home country and outside the home country.
+
+NOTE 2: MPS invocation using a UE with an MPS subscription is done using a predetermined method (e.g., by the Service User inclusion of an MPS-unique identifier or feature code as part of the request to establish an MPS for MMTEL voice call) that is recognized by the visited PLMN.
+
+A Service User using a UE that does not have an MPS subscription can invoke MPS to request priority for an MMTEL voice call or MMTEL voice conference call, e.g., when the normal MMTEL voice call or MMTEL voice conference call cannot be established.
+
+The system shall support means for a Service User using a UE that does not have a subscription for MPS to initiate MPS for an MMTEL voice call or MMTEL voice conference call.
+
+NOTE 3: MPS invocation using a UE that does not have an MPS subscription is done using a predetermined method that is outside the scope of 3GPP (e.g., by the Service User use of a predetermined access number, such as a special telephone number).
+
+A Service User who is the host of a MMTEL voice conference can invoke MPS to upgrade the entire MMTEL voice conference call to obtain priority treatment for all participants on the MMTEL voice conference call, e.g., when the normal MMTEL voice conference call cannot be established, or to upgrade an already established normal MMTEL conference call to MPS.
+
+The system shall support means for a Service User to:
+
+- initiate MPS for all participants of an MMTEL voice conference call, or
+- request upgrade of all participants of an ongoing MMTEL voice conference call to MPS.
+
+The system shall provide MPS for a late participant joining an MPS for MMTEL voice conference after MPS was activated for all participants.
+
+NOTE 4: When MPS is invoked for all participants of a MMTEL voice conference, the user priority level is based on the host MPS Service User, except in cases where an individual participant used MPS to join the conference with a higher user priority level, the higher user priority level is kept.
+
+NOTE 5: The invocation of MPS for all participants may be done using a customized feature of a voice conference service (available only to the host) that indicates a request for priority to the system.
+
+### 9.1.2.2 Revocation
+
+The 3GPP system shall revoke MPS for the following cases:
+
+- upon end of an MPS MMTEL voice call, or an MPS MMTEL voice conference call from a UE with an MPS subscription, and the UE shall return to normal conditions (i.e., use of normal MMTEL voice service),
+- upon end of an MPS MMTEL voice call, or an MPS MMTEL voice conference call from a UE that does not have an MPS subscription, and the UE shall return to normal conditions (i.e., use of normal voice service), and
+
+- upon end of an MPS MMTEL voice conference call where MPS was provided to all participants on the voice conference call, and the UEs shall return to normal conditions (i.e., use of normal MMTEL voice service).
+
+The 3GPP system shall revoke MPS for an individual participant leaving an ongoing MPS for MMTEL voice conference where MPS is activated for all participants.
+
+When an MPS MMTEL voice call or an MPS MMTEL voice conference call is not explicitly ended, upon UE detachment/deregistration (e.g., orderly power down), the system in the RPLMN shall automatically revoke MPS such that MPS priority treatment shall not automatically apply to subsequent calls upon subsequent registration.
+
+### 9.1.3 Authentication and authorization
+
+The system shall support means to authenticate and authorize an MPS MMTEL voice or voice conference call request from a UE with an MPS subscription.
+
+The system shall support means to authenticate and authorize a Service User request for an MPS MMTEL voice or voice conference call from a UE that does not have an MPS subscription.
+
+NOTE 1: The method for authenticating and authorizing the Service User using a UE that does not have an MPS subscription is predetermined. As part of the authentication and authorization process, the Service User provides MPS credentials (e.g., a calling card number, PIN or security token) specifically assigned for the purpose of obtaining MPS from a UE that does not have an MPS subscription.
+
+The system shall support means for a visited PLMN, including a visited PLMN within or outside of the home country, to verify with the home PLMN that a UE is authorized for MPS, and to authorize an MPS for MMTEL voice or voice conference call.
+
+NOTE 2: The method for authenticating and authorizing UE for MPS when roaming is based on operator policy and roaming agreements between the visited PLMN and home PLMN for MPS as per clause 5.8.
+
+The system shall support means to authenticate and authorize a Service User request to establish or upgrade all participants of an MMTEL voice conference call to MPS priority.
+
+### 9.1.4 Signalling
+
+The system shall provide priority treatment to the invocation signalling in the network once the request by the Service User for MPS for an MMTEL voice or MMTEL voice conference call is identified by the system.
+
+The system shall support a means for MPS activation when normal MMTEL voice service is congested at the request of the Service User.
+
+The system shall provide priority treatment to the affected signalling when MPS is activated for an MMTEL voice call, or MMTEL voice conference call.
+
+### 9.1.5 Media
+
+The system shall provide priority treatment to the audio media flows, when MPS is activated for an MMTEL voice call or MMTEL voice conference call.
+
+## 9.2 MPS for MMTEL video
+
+### 9.2.1 General
+
+The primary purpose of MPS for MMTEL video is to provide the Service User with priority video communication sessions in periods of severe network congestion during which normal commercial video service is degraded.
+
+The system shall support:
+
+- MPS for MMTEL video and video conference calls for an authorized Service User using a UE with a subscription for MPS,
+
+NOTE 1: The MPS subscription related information is associated with the UE's HPLMN subscription and is either stored in the UE and the HPLMN, or only in the HPLMN. In the case that the MPS subscription is stored in the UE, the UE's membership in a special access class as per TS 22.011 [6] is used for EUTRAN access to the EPC and membership in Access Identity 1 as per TS 22.261 [7] is used for 5G (NR and E-UTRAN access to the 5GC). In the case where the MPS subscription is stored only in the HPLMN (5GC), the HPLMN (5GC) can provide MPS indication during the UE registration.
+
+- MPS for MMTEL video and video conference calls for an authorized Service User using a UE that does not have an MPS subscription, and
+
+NOTE 2: In this case, the Service User's MPS subscription information (e.g., credentials) is not associated with the UE's HPLMN subscription. For example, the Service User borrows a UE that does not have an MPS subscription..
+
+- MPS for all participants of an authorized MMTEL video conference call.
+
+NOTE 3: MPS for all participants of an MMTEL video conference call allows a Service User (i.e., the host) to establish an MMTEL video conference with MPS for all participants, or upgrade an ongoing MMTEL video conference to MPS for all participants regardless of their subscription to MPS.
+
+## 9.2.2 Invocation and revocation
+
+### 9.2.2.1 Invocation
+
+A Service User, using a UE with an MPS subscription, can invoke MPS to request priority for an MMTEL video call or MMTEL video conference call, e.g., when the normal MMTEL video call cannot be established, or to upgrade an already established normal MMTEL call to MPS.
+
+The system shall support means for a Service User using a UE with an MPS subscription to:
+
+- initiate MPS for an MMTEL video call or an MPS MMTEL video conference call, or
+- request upgrade of an established MMTEL video call, or an established MMTEL video conference call to MPS.
+
+NOTE 1: MPS invocation using a UE with an MPS subscription is done using a predetermined method (e.g., by the Service User inclusion of an MPS-unique identifier or feature code as part of the request to establish an MPS for MMTEL video call).
+
+NOTE 2: In the case where the MMTEL video call is already established but becomes unacceptable, the invocation by the Service User to upgrade the MMTEL video call to MPS may be done using a specialized MPS application on the UE (i.e., as an alternative to releasing and retrying the call which may fail).
+
+A Service User, using a UE with an MPS subscription, can invoke MPS to request priority for an MMTEL video call or MMTEL video conference call during roaming, e.g., when the normal MMTEL video call cannot be established, or to upgrade an already established normal MMTEL video/conference call to MPS.
+
+The system shall support means for a Service User using a UE with an MPS subscription to:
+
+- initiate MPS for an MMTEL video call, or an MPS MMTEL video conference call when roaming within the home country and outside the home country, or
+- request upgrade of an established MMTEL video call, or an established MMTEL video conference call to MPS when roaming within the home country and outside the home country.
+
+NOTE 3: MPS invocation using a UE with an MPS subscription is done using a predetermined method (e.g., by the Service User inclusion of an MPS-unique identifier or feature code as part of the request to establish an MPS for MMTEL video call) that is recognized by the visited PLMN.
+
+NOTE 4: In the case where the MMTEL video call is already established but becomes unacceptable, the invocation by the Service User to upgrade the MMTEL video call to MPS may be done using a specialized MPS application on the UE (i.e., as an alternative to releasing and retrying the call which may fail) that is recognized by the visited PLMN.
+
+A Service User, using a UE that does not have an MPS subscription, can invoke MPS to request priority for an MMTEL video call or MMTEL video conference call, e.g., when the normal MMTEL video call, or MMTEL video conference call cannot be established
+
+The system shall support means for a Service User using a UE that does not have a subscription for MPS to initiate MPS for an MMTEL video call or MMTEL video conference call.
+
+NOTE 5: MPS invocation using a UE that does not have an MPS subscription is done using a predetermined method (e.g., by the Service User use of a predetermine access number, such as a special telephone number) and is outside the scope of 3GPP.
+
+A Service User who is the host of a MMTEL video conference can invoke MPS to upgrade the entire MMTEL video conference call to obtain priority treatment for all participants on the MMTEL video conference call, e.g., when the normal MMTEL video call cannot be established, or to upgrade an already established normal MMTEL video conference call to MPS.
+
+The system shall support means for a Service User to:
+
+- initiate MPS for all participants of an MMTEL video conference call, or
+- request upgrade of all participants of an ongoing MMTEL video conference call to MPS.
+
+The system shall provide MPS for a late participant joining an MPS for MMTEL video conference after MPS was activated for all participants.
+
+NOTE 6: When MPS is invoked for all participants of a MMTEL video conference, the user priority level is based on the host MPS Service User, except in cases where an individual participant used MPS to join the conference with a higher user priority level, the higher user priority level is kept.
+
+NOTE 7: The invocation of MPS for all participants may be done using a customized feature of a video conference service (available only to the host) that indicates a request for priority to the system.
+
+### 9.2.2.2 Revocation
+
+The 3GPP system shall revoke MPS for the following cases:
+
+- upon end of an MPS MMTEL video call, or an MPS MMTEL video conference call from a UE with an MPS subscription, and the UE shall return to normal conditions (i.e., use of normal MMTEL video service),
+- upon end of an MPS MMTEL video call, or an MPS MMTEL video conference call from a UE that does not have an MPS subscription, and the UE shall return to normal conditions (i.e., use of normal video service), and
+- upon end of an MPS MMTEL video conference call where MPS was provided to all participants on the video conference call, and the UEs shall return to normal conditions (i.e., use of normal MMTEL video service).
+
+The 3GPP system shall revoke MPS for an individual participant leaving an ongoing MPS for MMTEL video conference where MPS is activated for all participants.
+
+When an MPS MMTEL video call or an MPS MMTEL video conference call is not explicitly ended, upon UE detachment/deregistration (e.g., orderly power down), the 3GPP system in the RPLMN shall automatically revoke MPS such that MPS priority treatment shall not automatically apply to subsequent calls upon subsequent registration.
+
+### 9.2.3 Authentication and authorization
+
+The system shall support means to authenticate and authorize an MPS MMTEL video or video conference call request from a UE with an MPS subscription.
+
+The system shall support means to authenticate and authorize a Service User request for an MPS MMTEL video or video conference call from a UE that does not have an MPS subscription.
+
+NOTE 1: The method for authenticating and authorizing the Service User using a UE that does not have an MPS subscription is predetermined. As part of the authentication and authorization process, the Service User provides MPS credentials (e.g., a calling card number, PIN or security token) specifically assigned for the purpose of obtaining MPS from a UE that does not have an MPS subscription.
+
+The system shall support means for a visited PLMN, including a visited PLMN outside of the home country, to verify with the home PLMN that a UE is authorized for MPS, and to authorize an MPS for MMTEL video or video conference call.
+
+NOTE 2: The method for authenticating and authorizing UE for MPS when roaming is based on operator policy and roaming agreements between the visited PLMN and home PLMN for MPS as per clause 5.8.
+
+The system shall support means to authenticate and authorize a Service User request to establish or upgrade all participants of an MMTEL video conference call to MPS priority.
+
+## 9.2.4 Signalling
+
+The system shall provide priority treatment to the invocation signalling in the network once the request by the Service User for MPS for an MMTEL video or MMTEL video conference call is identified by the system.
+
+The system shall support a means for MPS activation when normal MMTEL video service is congested at the request of the Service User.
+
+The system shall provide priority treatment to the affected signalling when MPS is activated for an MMTEL video call, or MMTEL video conference call.
+
+## 9.2.5 Media
+
+The system shall provide priority treatment to the audio and video media flows, when MPS is activated for an MMTEL video call or MMTEL video conference call.
+
+The system shall support a means to differentiate the priority between the audio and video streams of a given MPS MMTEL video call.
+
+The system shall support a means to differentiate the priority between the audio and video streams of MPS participants (Service Users) on an MMTEL video conference call.
+
+The system shall retain the audio of an MPS for MMTEL video call or MMTEL video conference call when both the audio and video cannot be supported but the audio can be supported.
+
+The system shall support priority re-establishment of the video media when an MPS MMTEL video call, or an MPS MMTEL video conference call, is in progress with only audio media and the conditions which previously blocked the video media are no longer applicable.
+
+NOTE: This requirement does not imply the need to introduce a new IMS feature. It adds the need for priority treatment using the existing IMS feature for re-establishment of the video media.
+
+## 9.3 MPS for DTS
+
+### 9.3.1 General
+
+MPS for Data Transport Service (DTS) is a generic priority packet transport service that applies independently of the specific data application being used. It is a specific example of Priority Data Bearer Service described in clause 5.4a. MPS for DTS provides the Service User with priority for applications using the default bearer upon request (in the case of EPS), or QoS flow associated with the default QoS rule upon request (in the case of 5GS), to one or more selected active Packet Data Networks (PDNs)/Data Networks (DNs), in periods of severe network congestion during which normal commercial data service is degraded. MPS for DTS may also apply to other bearers (in the case of EPS) and other QoS Flows (in the case of 5GS) based on operator policy and regulatory rules.
+
+NOTE 1: Service Data Flows (SDFs) previously mapped to the default bearer (in case of EPS) / QoS flow associated with the default QoS rule (in case of 5GS), are upgraded to MPS priority.
+
+The system shall support:
+
+- MPS for DTS for an authorized Service User using a UE with a subscription for MPS, and
+
+NOTE 2: The MPS subscription related information is associated with the UE's HPLMN subscription and is either stored in the UE and the HPLMN, or only in the HPLMN. In the case that the MPS subscription is stored in the UE, the UE's membership in a special access class as per TS 22.011 [6] is used for EUTRAN access to the EPC and membership in Access Identity 1 as per TS 22.261 [7] is used for 5G (NR and E-UTRAN access to the 5GC). In the case where the MPS subscription is stored only in the HPLMN (5GC), the HPLMN (5GC) can provide MPS indication during the UE registration.
+
+- MPS for DTS for an authorized Service User using a UE that does not have an MPS subscription.
+
+NOTE 3: In this case, the Service User's MPS subscription information (e.g., credentials) is not associated with the UE's HPLMN subscription. For example, the Service User borrows a UE that does not have an MPS subscription..
+
+MPS for DTS may be used to by a Service User to obtain priority access (e.g., Virtual Private Network (VPN) access) to an enterprise network (e.g., a private corporate network or private Government Agency network to download data and/or access enterprise applications such as email, text/chat/presence, voice and video).
+
+The system shall support for an authorised Service User, an end-to-end MPS for DTS connection between the MPS subscribed UE and an associated enterprise network supporting MPS on demand based on operator policy and when agreements are in place for MPS.
+
+NOTE 4: The end-to-end MPS for DTS connection between the UE and an associated enterprise network is supported either using a web browser (e.g., use of a predetermined address (i.e., URL) in a web browser) or using a user-selectable option provided as part of the VPN client in the UE with an MPS subscription.
+
+MPS for DTS provides an IoT device with subscription to MPS with priority for applications using a specific default bearer (in the case of EPS), or default QoS flow (in the case of 5GS), towards a single specified PDN/DN; in the case of IoT connectivity to an enterprise, MPS also provides priority for the terminating access network (connected to the enterprise).
+
+The system shall support:
+
+- MPS for DTS for an authorized IoT device with a subscription for MPS, and
+- an end-to-end MPS for DTS connection between the MPS subscribed IoT device and an associated enterprise network supporting MPS on demand based on operator policy when agreements are in place for MPS.
+
+NOTE 5: An MPS specialized application on the MPS subscribed IoT device is used to support MPS for DTS through machine interactions that may not directly involve a human Service User.
+
+An authorized enterprise network supporting MPS uses MPS for DTS to activate priority for remote MPS subscribed UEs and MPS subscribed IoT devices associated with the enterprise network based on operator policy when agreements are in place for MPS.
+
+The system shall support:
+
+- for an authorized enterprise network supporting MPS, activation of MPS for DTS for remote MPS subscribed UEs associated with the enterprise network on demand based on operator policy when agreements are in place for MPS, and
+- for an authorized enterprise network supporting MPS, activation of MPS for DTS for remote MPS subscribed IoT devices associated with the enterprise network on demand based on operator policy when agreements are in place for MPS.
+
+NOTE 6: MPS for DTS activation by an authorized enterprise network supporting MPS involves prearrangement and configuration (i.e., subscription arrangement identifying the enterprise network authorization for remote activation of DTS in IoT devices) within the MPS Service Provider PLMN.
+
+## 9.3.2 Invocation and revocation
+
+### 9.3.2.1 Invocation
+
+A Service User, using a UE with an MPS subscription, can invoke MPS for DTS to request priority, e.g., when the normal data session cannot be established, or to upgrade an already established normal data session to MPS.
+
+The system shall support means for a Service User using a UE with an MPS subscription to initiate MPS for a DTS session.
+
+NOTE 1: MPS invocation using a UE with an MPS subscription is done using a predetermined method (e.g., by the Service User using a web browser to enter a predetermined address such as an URL).
+
+A Service User, using a UE with an MPS subscription, can invoke MPS to request priority during roaming, e.g., when the normal data sessions cannot be established, or to upgrade an already established normal data session to MPS.
+
+The system shall support means for a Service User using a UE with an MPS subscription to initiate MPS for DTS session when roaming within the home country and outside the home country.
+
+NOTE 2: MPS for DTS invocation using a UE with an MPS subscription is done using a predetermined method (e.g., by the Service User using a web browser to enter a predetermined address such as an URL) recognized by the visited PLMN.
+
+A Service User, using a UE that does not have an MPS subscription, can invoke MPS for DTS to request priority, e.g., when the normal data session cannot be established, or to upgrade an already established normal data session to MPS.
+
+The system shall support means for a Service User using a UE that does not have a subscription for MPS to initiate MPS for DTS.
+
+NOTE 3: MPS for DTS invocation using a UE that does not have an MPS subscription is done using a predetermined method (e.g., by the Service User use of a predetermine URL address) and is outside the scope of 3GPP.
+
+A Service User, using a UE with an MPS subscription, can invoke MPS for DTS to obtain priority for Virtual Private Network (VPN) access to an enterprise network (e.g., a Government Agency private enterprise network), e.g., when normal data session cannot be established or is degraded.
+
+The system shall support means for a Service User using a UE with an MPS subscription to initiate an MPS for DTS session to an associated enterprise network supporting MPS on demand based on operator policy and when agreements are in place for MPS.
+
+NOTE 4: Invocation of MPS for DTS is done either using a web browser (e.g., use of a predetermined address (i.e., URL) in a web browser) or using a user-selectable option provided as part of the VPN client in the UE with an MPS subscription.
+
+An IoT device with an MPS subscription can invoke MPS for DTS to request priority when normal data service is degraded.
+
+The system shall support means for an IoT device with an MPS subscription to initiate an MPS for DTS session to an enterprise network supporting MPS.
+
+NOTE 5: An MPS specialized application on the MPS subscribed IoT device is responsible for determining whether or not to invoke MPS for DTS in support of the data communication needs. The MPS specialized application allows invocation/revocation of the DTS through machine interactions that may not directly involve a human Service User.
+
+An authorized enterprise network supporting MPS activates MPS for DTS to request priority for MPS subscribed UEs and MPS subscribed IoT devices associated with the enterprise network when normal data service is unacceptable.
+
+The 3GPP system shall support means for an authorized enterprise network supporting MPS to request activation of MPS for DTS for the following cases:
+
+- a specific MPS subscribed UE or IoT device, and
+- a group of MPS subscribed UEs or IoT devices.
+
+NOTE 6: MPS for DTS invocation done by the enterprise network supporting MPS involves prearrangement and configuration (i.e., subscription arrangement identifying the enterprise network authorization for remote activation of DTS in IoT devices) within the MPS Service Provider PLMN. For example, an MPS specialized application hosted in the enterprise network (e.g., IoT application server) may be responsible for determining whether or not to invoke MPS for DTS. The MPS specialized application allows invocation/revocation of the DTS through machine interactions that may not directly involve a human Service User.
+
+The system shall support receiving and authenticating MPS for DTS invocation requests from authorized MPS Service Users via public non-3GPP networks.
+
+NOTE 7: The intent of the above requirement is to allow an authorized MPS Service User to send a request via the Internet to establish an MPS for DTS session for one or more active PDNs/DNs of a UE.
+
+The system shall support discovery and selection of active data connections upon receipt of an MPS for DTS invocation request by an authorized MPS Service User.
+
+### 9.3.2.2 Revocation
+
+The system shall support means to release an MPS for DTS session for the cases:
+
+- an MPS Service User using a UE with an MPS subscription,
+- an MPS Service User using a UE that does not have an MPS subscription, and
+- an IoT device with an MPS subscription.
+
+The system shall support means for an authorized enterprise network supporting MPS to explicitly request to release an MPS for DTS session or group of MPS for DTS sessions while maintaining basic connectivity to the MPS subscribed UE(s) or IoT device(s).
+
+The system shall support means for an MPS Service User to explicitly release an MPS for DTS session from a UE with an MPS subscription when roaming, including outside the home country.
+
+If MPS for DTS is not explicitly revoked by the Service User or an IoT device, the system in the RPLMN shall automatically revoke MPS:
+
+- upon UE detachment/deregistration (e.g., power down), or
+- when all the connections pertaining to the MPS for DTS session are released (without explicit release of the MPS for DTS session).
+
+The system shall automatically revoke MPS when the maximum allowed duration for an MPS for DTS session is reached.
+
+### 9.3.3 Authentication and authorization
+
+The system shall support means to authenticate and authorize an MPS for DTS session request from a UE with an MPS subscription.
+
+The system shall support means to authenticate and authorize a Service User request for an MPS for DTS session from a UE that does not have an MPS subscription.
+
+NOTE 1: The method for authenticating and authorizing the Service User using a UE that does not have an MPS subscription is predetermined. As part of the authentication and authorization process, the Service User provides MPS credentials (e.g., PIN or security token) specifically assigned for the purpose of obtaining MPS from a UE that does not have an MPS subscription.
+
+The system shall support means for a visited PLMN, including a visited PLMN outside of the home country, to verify with the home PLMN that a UE is authorized for MPS, and to authorize an MPS for DTS session.
+
+NOTE 2: The method for authenticating and authorizing UE for MPS when roaming is based on operator policy and roaming agreements between the visited PLMN and home PLMN for MPS as per clause 5.8.
+
+The system shall support means to authenticate and authorize an MPS for DTS session request from an IoT device with an MPS subscription.
+
+The system shall support means to authenticate and authorise an enterprise network supporting MPS requesting activation of MPS for DTS for the following cases:
+
+- a specific MPS subscribed UE or IoT device, and
+- a group of MPS subscribed UEs or IoT devices.
+
+### 9.3.4 Signalling
+
+The system shall provide priority treatment to the invocation signalling in the network once the MPS for DTS request is identified by the system.
+
+The system shall support a means for MPS for DTS activation when normal data service is congested.
+
+### 9.3.5 Media
+
+The system shall provide priority treatment to the affected media flows when an MPS for DTS session is activated.
+
+The system shall provide priority treatment to the affected media flows when MPS for DTS is activated for the connection between an MPS subscribed UE or IoT device and an associated enterprise network supporting MPS.
+
+NOTE: Both the MPS subscribed UE or IoT device and the enterprise network must be served by the same PLMN.
+
+### 9.3.6 QoS
+
+The system shall be capable of supporting a set of default QoS characteristics for an active MPS for DTS session.
+
+The system shall be capable of verifying authorization for a requested QoS modification to an active MPS for DTS session.
+
+The system shall be capable of making authorized QoS modifications in support of MPS for DTS for all media traffic supported via the default bearer (in the case of EPS), or the default QoS flow (in the case of 5GS).
+
+The system shall support means to allow a Service User to request QoS modifications for an active MPS for DTS session.
+
+The system shall support means to provide a Service User with an indication that a requested QoS modification of an active MPS for DTS session was successful.
+
+### 9.3.7 Security
+
+The system shall support security capabilities to verify an enterprise network's authorization to request MPS for DTS activation.
+
+---
+
+## 9.4 MPS for Messaging Services
+
+### 9.4.1 General
+
+MPS for Messaging provides priority for messaging services in periods of network congestion during which normal commercial messaging services are degraded.
+
+The system shall support MPS priority for messaging services supported using IMS Messaging, SMS and/or MMS, or MSGin5G for an authorized Service User using a UE with a subscription for MPS.
+
+NOTE 1: MPS for Messaging may make use of commercial messaging service offerings provided by the operator. However, the messaging service applications are not in scope.
+
+NOTE 2: The MPS Service User might not know whether the messaging service is supported using IMS Messaging, SMS and/or MMS, or MSGin5G.
+
+NOTE 3: SMS options in scope are SMS via NAS and SMS over IP (i.e., SMS over MAP and SMS over SGs are not in scope).
+
+The system shall support MPS priority for messaging using SMS and/or MMS or MSGin5G for an authorized IoT device with a subscription for MPS.
+
+NOTE 4: An MPS specialized application on the MPS subscribed IoT device is used to support MPS for Messaging through machine interactions that might not directly involve a human Service User.
+
+## 9.4.2 Invocation and revocation
+
+### 9.4.2.1 Invocation
+
+A Service User using a UE with an MPS subscription can activate MPS for Messaging to request priority, e.g., when the normal messaging service is degraded.
+
+The system shall support means for a Service User using a UE with an MPS subscription to activate MPS for Messaging.
+
+NOTE 1: MPS for Messaging invocation is done using a predetermined method (e.g., by the Service User using a web browser to enter a predetermined address such as an URL or sending a message to the MPS operator to activate MPS for Messaging).
+
+A Service User using a UE with an MPS subscription can invoke MPS for Messaging to request priority during roaming, e.g., when the normal messaging service is degraded.
+
+The system shall support means for a Service User using a UE with an MPS subscription to activate MPS for Messaging when roaming within the home country and outside the home country.
+
+NOTE 2: MPS for Messaging invocation is done using a predetermined method recognized by the visited PLMN.
+
+An IoT device with an MPS subscription can invoke MPS for Messaging to request priority when normal messaging service is degraded.
+
+The system shall support means for an authorized IoT device with an MPS subscription to activate MPS for Messaging.
+
+NOTE 3: An MPS specialized application on the MPS subscribed IoT device is responsible for determining whether or not to invoke MPS for Messaging in support of the text communication needs. The MPS specialized application allows invocation/revocation of MPS for Messaging through machine interactions that might not directly involve a human Service User.
+
+An authorized enterprise network supporting MPS activates MPS for Messaging to request priority for MPS subscribed UEs and MPS subscribed IoT devices associated with the enterprise network when normal messaging service is degraded.
+
+The system shall support means for an authorized enterprise network supporting MPS to request activation of MPS for Messaging for the following cases:
+
+- a specific MPS subscribed UE or MPS subscribed IoT device, and
+- a group of MPS subscribed UEs or MPS subscribed IoT devices.
+
+NOTE 4: MPS for Messaging invocation done by the enterprise network supporting MPS involves prearrangement and configuration (i.e., subscription arrangement identifying the enterprise network authorization for remote activation of MPS for Messaging) within the MPS Service Provider PLMN. For example, an MPS specialized application hosted in the enterprise network (e.g., IoT application server) might be responsible for determining whether or not to invoke MPS for Messaging. The MPS specialized application allows invocation/revocation of MPS for Messaging through machine interactions that might not directly involve a human Service User.
+
+The system shall support receiving and authenticating MPS for Messaging invocation requests from authorized MPS Service Users using UEs with an MPS subscription and authorized IoT devices with an MPS subscription via public non-3GPP networks.
+
+NOTE 4: The intent of the above requirement is to allow an authorized MPS Service User or authorized IoT device to send a request via the Internet to activate or enable MPS for Messaging.
+
+Based on national/regional regulatory rules and operator policy, the system shall support means to activate:
+
+- MPS for Messaging separately from MPS for DTS described in clause 9.2, or
+- MPS for Messaging and MPS for DTS together.
+
+NOTE 5: The intent of the above requirement is to allow the MPS Service Provider flexibility to activate/revoke MPS for Messaging and MPS for DTS separately or in combination.
+
+### 9.4.2.2 Revocation
+
+The system shall support means to revoke MPS for Messaging for the cases:
+
+- a Service User using a UE with an MPS subscription, and
+- an IoT device with an MPS subscription.
+
+The system shall support means for an authorized enterprise network supporting MPS to explicitly request to revoke MPS for Messaging for a individual or group of MPS subscribed UEs or MPS subscribed IoT devices while maintaining basic connectivity to the MPS subscribed UE(s) or MPS subscribed IoT device(s).
+
+The system shall support means for a Service User to explicitly revoke MPS for Messaging from a UE with an MPS subscription when roaming, including outside the home country.
+
+If MPS for Messaging is not explicitly revoked by the Service User or IoT device, the system in the RPLMN shall automatically revoke MPS upon UE detachment/deregistration (e.g., power down).
+
+The system shall support means for an authorized IoT device with an MPS subscription to revoke MPS for Messaging.
+
+The system shall automatically revoke MPS when the maximum allowed duration for MPS for Messaging is reached.
+
+Based on national/regional regulatory rules and operator policy, the system shall support means to revoke:
+
+- MPS for Messaging separately from MPS for DTS described in clause 9.2, or
+- MPS for Messaging and MPS for DTS together.
+
+NOTE 5: The intent of the above requirement is to allow the MPS Service Provider flexibility to activate/revoke MPS for Messaging and MPS for DTS separately or in combination.
+
+### 9.4.3 Authentication and authorization
+
+The system shall support means to authenticate and authorize an MPS for Messaging activation request from a UE with an MPS subscription.
+
+The system shall support means for a visited PLMN, including a visited PLMN outside of the home country, to verify with the home PLMN that a UE is authorized for MPS, and to authorize MPS for Messaging.
+
+NOTE 1: The MPS subscription related information is associated with the UE's HPLMN subscription and is either stored in the UE and the HPLMN, or only in the HPLMN. In the case that the MPS subscription is stored in the UE, the UE's membership in a special access class as per TS 22.011 [6] is used for EUTRAN access to the EPC and membership in Access Identity 1 as per TS 22.261 [7] is used for 5G (NR and E-UTRAN access to the 5GC). In the case where the MPS subscription is stored only in the HPLMN (5GC), the HPLMN (5GC) can provide MPS indication during the UE registration.
+
+NOTE 2: The method for authenticating and authorizing a UE for MPS when roaming is based on operator policy and roaming agreements between the visited PLMN and home PLMN for MPS as per clause 5.8.
+
+The system shall support means to authenticate and authorize an MPS for Messaging activation request from an IoT device with an MPS subscription.
+
+The system shall support means to authenticate and authorise an enterprise network that supports MPS when it requests activation of MPS for Messaging for the following cases:
+
+- a specific MPS subscribed UE or MPS subscribed IoT device, and
+- a group of MPS subscribed UEs or MPS subscribed IoT devices.
+
+### 9.4.4 Signalling
+
+The system shall provide priority treatment to the invocation signalling in the network once the MPS for Messaging request is identified by the system.
+
+The system shall support a means for MPS for Messaging activation when normal messaging service is congested.
+
+## 9.4.5 Message origination and termination
+
+### 9.4.5.1 IMS Messaging
+
+When MPS for Messaging is authorized and activated for an originating UE with a subscription for MPS using IMS Messaging for the messaging service, the system shall provide:
+
+- end to end priority treatment for point to point messages when the recipient(s) is using IMS Messaging regardless whether the recipient(s) have a subscription for MPS, and
+- priority treatment for messages to/from the Message Service Center.
+
+When MPS for Messaging is authorized and activated for a terminating UE with a subscription for MPS using IMS Messaging for the messaging service, the system shall provide priority treatment for all messages to/from the Message Service Center.
+
+When a terminating network receives an incoming message with an MPS for Messaging indication, the message shall receive priority treatment in the terminating PLMN.
+
+NOTE: End to end priority can be provided by the 3GPP system for the point to point messages when both the originating UE and the destination UE are using IMS Messaging service. When the originating UE is using IMS Messaging service but the destination UE is not using IMS Messaging service, priority treatment is provided by the 3GPP system only to/from the Message Service Center.
+
+### 9.4.5.2 SMS and MMS
+
+When MPS for Messaging is authorized and activated for a UE or IoT device with a subscription for MPS using SMS or MMS for the messaging service, the system shall provide priority treatment for all messages to/from the Message Service Center.
+
+NOTE 1: The SMS and MMS platforms and inter system aspects are outside 3GPP scope.
+
+NOTE 2: The above requirement is not applicable for SMS over MAP and SMS over SGs.
+
+### 9.4.5.3 MSGin5G
+
+When MPS for Messaging is authorized and activated for an originating UE or IoT device with a subscription for MPS using MSGin5G for the messaging service, the system shall provide:
+
+- end to end priority treatment for point to point messages when the recipient(s) is using MSGin5G regardless whether the recipient(s) have a subscription for MPS, and
+- priority treatment for messages to/from the Message Service Center.
+
+When MPS for Messaging is authorized and activated for a terminating UE or IoT device with a subscription for MPS using MSGin5G for the messaging application service, the system shall provide priority treatment for all messages to/from the Message Service Center.
+
+When a terminating network receives an incoming message with an MPS for Messaging indication, the message shall receive priority treatment in the terminating PLMN.
+
+NOTE 1: End to end priority can be provided by the 3GPP system for the point to point messages when both the originating UE and the destination UE are using MSGin5G service. When the originating UE is using MSGin5G but the destination UE is not using MSGin5G, priority treatment is provided by the 3GPP system only to/from the Message Service Center.
+
+NOTE 2: MSGin5G is only applicable to 5GS.
+
+## 9.4.8 Security
+
+The system shall support security capabilities to verify an enterprise network's authorization to request MPS for Messaging activation.
+
+---
+
+## 10 Non-3GPP access
+
+### 10.1 MPS when access to the EPC/5GC is WLAN
+
+MPS can be supported for MMTEL voice/video calls and data sessions when the access to the EPC/5GC is WLAN and the 3GPP system is used for the MPS authorization. In this case, MPS priority treatment can be provided by:
+
+- both the WLAN access and the EPC/5GC (i.e., when the WLAN supports MPS), or
+- only the EPC/5GC (i.e., when the WLAN does not support MPS).
+
+The following subclauses provide requirements specific to WLAN access to EPC/5GC.
+
+#### 10.1.1 MPS for MMTEL voice and video
+
+##### 10.1.1.1 General
+
+For a UE with WLAN access to the EPC/5GC, the system shall support the requirements in clauses 9.1 and 9.2 for MMTEL voice and voice conference calls and MMTEL video and video conference calls by an authorized MPS Service User using
+
+- a UE with a subscription for MPS, and
+- a UE that does not have an MPS subscription.
+
+The system shall support the requirements in clauses 9.1 and 9.2 for MPS for MMTEL voice and voice conference calls and MPS for MMTEL video and video conference calls terminating to a UE with WLAN access to the EPC/5GC regardless of the terminating UE subscription for MPS.
+
+##### 10.1.1.2 Authentication and authorization
+
+For a UE with a 3GPP subscription for MPS and with WLAN access to the EPC/5GC, the system shall support MPS for MMTEL voice/video authorization based on the UE subscription information.
+
+For a UE that does not have a 3GPP subscription for MPS and with WLAN access to the EPC/5GC, the system shall support MPS for MMTEL voice/video authorization based on Service User credentials not associated with the UE (e.g., a calling card number, PIN or security token).
+
+##### 10.1.1.3 WLAN Interworking
+
+For a UE with WLAN access to the EPC/5GC, the 3GPP system shall support delivery of the following to the WLAN:
+
+- indication of MPS for MMTEL voice/video authorization,
+- priority marking of transport parameters of MPS for MMTEL voice/video signalling and media, and
+- QoS characteristics of MPS for MMTEL voice/video signalling and media.
+
+#### 10.1.2 MPS for DTS
+
+##### 10.1.2.1 General
+
+For a UE or IoT device with WLAN access to the EPC/5GC, the system shall support the requirements in clause 9.3 on MPS for DTS sessions for:
+
+- an authorized Service User using a UE with a subscription for MPS,
+- an authorized Service User using a UE that does not have an MPS subscription,
+- an authorized IoT device with a subscription for MPS, and
+- an authorized enterprise network activation of MPS for DTS for remote MPS subscribed UEs/IoT devices associated with the enterprise network.
+
+### 10.1.2.2 Authentication and authorization
+
+For a UE or IoT device with a 3GPP subscription for MPS and with WLAN access to the EPC/5GC, the system shall support MPS for DTS authorization based on the UE subscription information.
+
+For a UE that does not have a 3GPP subscription for MPS and with WLAN access to the EPC/5GC, the system shall support MPS for DTS authorization based on Service User credentials not associated with the UE (e.g., a calling card number, PIN or security token).
+
+For an authorized enterprise network that is activating MPS for DTS for a remote UE or IoT device with a 3GPP subscription for MPS, the system shall support MPS for DTS authorization based on the UE or IoT device subscription information.
+
+### 10.1.2.3 WLAN interworking
+
+For a UE or IoT with WLAN access to the EPC/5GC, the 3GPP system shall support delivery of the following to the WLAN:
+
+- indication of MPS for DTS authorization,
+- priority marking of transport parameters of MPS for DTS signalling and media, and
+- QoS characteristics of MPS for DTS signalling and media.
+
+### 10.1.3 Void
+
+## 10.1.4 MPS for Messaging services
+
+### 10.1.4.1 General
+
+For a UE or IoT device with WLAN access to the EPC/5GC, the system shall support the requirements in clause 9.4 on MPS for Messaging supported using IMS Messaging, SMS and/or MMS, or MSGin5G.
+
+### 10.1.4.2 Authentication and authorization
+
+For a UE or IoT device with a 3GPP subscription for MPS and with WLAN access to the EPC/5GC, the system shall support MPS for Messaging authorization based on the UE subscription information.
+
+For an authorized enterprise network that is activating MPS for Messaging for a remote UE or IoT device with a 3GPP subscription for MPS, the system shall support MPS for Messaging authorization based on the UE or IoT device subscription information.
+
+### 10.1.4.3 WLAN interworking
+
+For a UE or IoT with WLAN access to the EPC/5GC, the 3GPP system shall support delivery of the following to the WLAN:
+
+- indication of MPS for Messaging authorization,
+- priority marking of transport parameters of MPS for Messaging signalling and media, and
+- QoS characteristics of MPS for Messaging signalling and media.
+
+---
+
+## 11 MPS support in 3GPP system with satellite
+
+MPS can be supported in 3GPP systems with satellite. Support of MPS when the UE/IoT device has satellite access is important during certain disaster scenarios such as when terrestrial access networks are unavailable or degraded. In some cases, satellite might be the only available access (e.g., remote areas with only satellite coverage or during terrestrial access network failure) and therefore critical for MPS communications.
+
+The following subclauses provide requirements specific to MPS support in 3GPP systems with satellite (e.g., satellite access to EPC/5GC).
+
+NOTE: The following conditions apply to all requirements in clause 11:
+
+- MPS support is subject to regulatory rules,
+- MPS is supported by terrestrial operator policy,
+- MPS is supported by satellite operator policy (if the satellite operator is not the terrestrial operator), and
+- MPS is supported by terrestrial operator and satellite operator agreements (if any).
+
+### 11.1 MPS for MMTEL voice and video
+
+#### 11.1.1 General
+
+The 3GPP system with satellite shall support MPS for MMTEL voice and video as specified in clause 9.1 and 9.2.
+
+#### 11.1.2 Service continuity
+
+The 3GPP system shall support MPS for MMTEL voice/video continuity when features for service continuity as specified in clause 6.46.3 of TS 22.261 [7] are supported within a satellite network (e.g., ISLs), between satellite networks, and between a terrestrial access network and a satellite access network.
+
+### 11.2 MPS for DTS
+
+#### 11.2.1 General
+
+The 3GPP system with satellite shall support MPS for DTS as specified in clause 9.3.
+
+#### 11.2.2 Service continuity
+
+The 3GPP system shall support MPS for DTS continuity when features for service continuity as specified in clause 6.46.3 of TS 22.261 [7] are supported within a satellite network (e.g., ISLs), between satellite networks, and between a terrestrial access network and a satellite access network.
+
+### 11.3 MPS for Messaging services
+
+#### 11.3.1 General
+
+The 3GPP system with satellite shall support MPS for Messaging services as specified in clause 9.4.
+
+#### 11.3.2 Service continuity
+
+The 3GPP system shall support MPS for Messaging continuity when features for service continuity as specified in clause 6.46.3 of TS 22.261 [7] are supported within a satellite network (e.g., ISLs), between satellite networks, and between a terrestrial access network and a satellite access network.

marked/Rel-20/22_series/22268/raw.md

@@ -0,0 +1,617 @@
+
+
+
+
+
+
+# Contents
+
+|                                                                                                              |    |
+|--------------------------------------------------------------------------------------------------------------|----|
+| Foreword                                                                                                     | 5  |
+| 1 Scope                                                                                                      | 6  |
+| 2 References                                                                                                 | 6  |
+| 3 Definitions and abbreviations                                                                              | 7  |
+| 3.1 Definitions                                                                                              | 7  |
+| 3.2 Abbreviations                                                                                            | 7  |
+| 4 General PWS Requirements                                                                                   | 7  |
+| 4.1 Background                                                                                               | 7  |
+| 4.2 High level general requirements for Warning Notification delivery                                        | 8  |
+| 4.3 Warning Notification Content                                                                             | 8  |
+| 4.4 Granularity of the distribution                                                                          | 8  |
+| 4.5 Support of Warning Notification Providers                                                                | 9  |
+| 4.6 PWS-UE Requirements                                                                                      | 9  |
+| 4.6.1 General Requirements                                                                                   | 9  |
+| 4.6.2 Support of non-Warning Notification capable UEs                                                        | 9  |
+| 4.6.3 Battery Life of PWS-UE                                                                                 | 10 |
+| 4.6.4 Enabling and disabling of Warning Notifications                                                        | 10 |
+| 4.7 Roaming Requirements                                                                                     | 10 |
+| 4.8 Security Requirements                                                                                    | 10 |
+| 4.9 Regulatory Requirements                                                                                  | 11 |
+| 5 Earthquake and Tsunami Warning System                                                                      | 11 |
+| 5.1 Background                                                                                               | 11 |
+| 5.2 Duration of delivery time                                                                                | 11 |
+| 5.3 Information element and volume                                                                           | 11 |
+| 5.4 Priority                                                                                                 | 12 |
+| 5.5 Roaming users                                                                                            | 12 |
+| 6 CMAS Specific Requirements                                                                                 | 13 |
+| 6.1 Introduction to CMAS                                                                                     | 13 |
+| 6.2 Additional PWS Requirements Specific to CMAS                                                             | 14 |
+| 7 EU-ALERT Specific Requirements                                                                             | 15 |
+| 7.1 Introduction to EU-ALERT                                                                                 | 15 |
+| 7.2 Additional PWS Requirements Specific to EU-ALERT                                                         | 15 |
+| 8 Korean Public Alert System specific Requirements                                                           | 16 |
+| 8.1 Introduction to Korean Public Alert System                                                               | 16 |
+| 8.2 Additional PWS Requirements Specific to Korean Public Alert System (KPAS)                                | 16 |
+| 9 Enhancements of Public Warning System (ePWS)                                                               | 17 |
+| 9.1 Service description                                                                                      | 17 |
+| 9.2 General Requirements                                                                                     | 17 |
+| 9.2.1 ePWS Requirements                                                                                      | 17 |
+| 9.2.2 Battery Life of ePWS-UE                                                                                | 18 |
+| 9.2.3 Enabling and disabling of Warning Notifications                                                        | 18 |
+| 9.3 Requirements for 3GPP system supporting ePWS-UEs                                                         | 18 |
+| 9.4 Requirements for ePWS-UE incapable of displaying text based Warning Notification                         | 18 |
+| 9.4.1 Requirements for ePWS-UE with no user interface                                                        | 18 |
+| 9.4.2 Requirements for ePWS-UE with a user interface incapable of displaying text based Warning Notification | 19 |
+| 9.5 Requirements for the improvement of understanding the Warning Notification                               | 19 |
+| 10 Relay of Warning Notification                                                                             | 19 |
+| 10.1 Service description                                                                                     | 19 |
+| 10.2 Requirements for the relay functionality                                                                | 19 |
+| 11 Chinese Public Alert System Specific Requirements                                                         | 20 |
+| 11.1 Introduction to Chinese Public Alert System (CPAS)                                                      | 20 |
+
+|                        |                                              |    |
+|------------------------|----------------------------------------------|----|
+| 11.2                   | Additional PWS Requirements Specific to CPAS | 20 |
+| Annex A (informative): | Change history                               | 21 |
+
+---
+
+# Foreword
+
+This Technical Specification has been produced by the 3<sup>rd</sup> Generation Partnership Project (3GPP).
+
+The contents of the present document are subject to continuing work within the TSG and may change following formal TSG approval. Should the TSG modify the contents of the present document, it will be re-released by the TSG with an identifying change of release date and an increase in version number as follows:
+
+Version x.y.z
+
+where:
+
+- x the first digit:
+  - 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.
+
+---
+
+# 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 complete service. This TS also covers subsystem additional requirements for the Earthquake and Tsunami Warning System (ETWS), the Commercial Mobile Alert System (CMAS), EU-ALERT, and Korean Public Alert System (KPAS).
+
+This TS includes information applicable to network operators, service providers, terminal and network manufacturers, in case of deployment of PWS, ETWS, and or CMAS, EU-ALERT, and KPAS. PWS, ETWS, CMAS, EU-ALERT, and KPAS deployment depends on operator decision or national regulations.
+
+---
+
+# 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] FCC 08-99: "Federal Communications Commission First Report and Order In the Matter of The Commercial Mobile Alert System"; April 9, 2008.
+- [2] FCC 08-164: "Federal Communications Commission Second Report and Order and Further Notice of Proposed Rulemaking In the Matter of The Commercial Mobile Alert System"; July 8, 2008.
+- [3] FCC 08-184: "Federal Communications Commission Third Report and Order and Further Notice of Proposed Rulemaking In the Matter of The Commercial Mobile Alert System"; August 7, 2008.
+- [4] J-STD-100: "Joint ATIS/TIA-CMAS Mobile Device Behavior Specification"; January 30, 2009.
+- [5] 3GPP TR 21.905: "Vocabulary for 3GPP Specifications".
+- [6] ETSI TS 102 900: "European Public Warning System (EU-ALERT) using the Cell Broadcast Service".
+- [7] TTA TTAK.KO-06.0263:"Requirements and Message Format for Korean Public Alert System over Mobile Network".
+- [8] FCC 16-127, Federal Communications Commission Report and Order and Further Notice of Proposed Rulemaking In the Matter of Wireless Emergency Alerts Amendments to Part 11 of the Commission's Rules Regarding the Emergency Alert System; September 29, 2016.
+- [9] 3GPP TS 23.038; "Alphabets and language-specific information"
+- [10] FCC 18-4, Federal Communications Commission Second Report and Order and Second Order on Reconsideration In the Matter of Wireless Emergency Alerts and Amendments to Part 11 of the Commission's Rules Regarding the Emergency Alert System; January 30, 2018
+- [11] 3GPP TS 22.071: "Location Services (LCS); Service description; Stage 1"
+
+---
+
+## 3 Definitions and abbreviations
+
+### 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 System that delivers *Warning Notifications* provided by *Warning Notification Providers* to CMAS capable PWS-UEs. CMAS defines the following classes of Warning Notifications: Presidential, Imminent Threat, Public Safety, Child Abduction Emergency, and State/Local WEA Test.
+
+**Earthquake and Tsunami Warning System:** Public Warning System that delivers *Warning Notifications* specific to Earthquake and Tsunami provided by *Warning Notification Providers* to the UEs which have the capability of receiving Primary and Secondary *Warning Notifications* within *Notification Areas* through the 3GPP network
+
+**Notification Area:** area where *Warning Notifications* are broadcast. This is an area that closely approximates the geographical information provided by the Warning Notification Provider
+
+**PWS-UE:** User Equipment (UE) which has the capability of receiving Warning Notifications within Notification Areas through the 3GPP network and conforms to the behaviour specific to the PWS service such as dedicated alerting indication and display of the Warning Notification upon reception
+
+**ePWS-UE:** User Equipment (UE) that supports the ePWS functionality
+
+### 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 Service                |
+| CMAS | Commercial Mobile Alert System        |
+| CPAS | Chinese Public Alert System           |
+| EOC  | Emergency Operations Center           |
+| ETWS | Earthquake and Tsunami Warning System |
+| KPAS | Korean Public Alert System            |
+| PWS  | Public Warning System                 |
+| WEA  | Wireless Emergency Alert              |
+| ePWS | enhancements of Public Warning System |
+
+---
+
+## 4 General PWS Requirements
+
+### 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, hurricanes and wild fires; such a capability is essential to enable the public to take appropriate action to protect their families and themselves from serious injury, or loss of life or property.
+
+This interest to enhance the reliability, resiliency, and security of Warning Notifications to the public by providing a mechanism to distribute Warning Notifications over 3GPP systems is the impetus for this Public Warning System Technical Specification.
+
+NOTE 1: PWS can be supported in NB-IoT terrestrial network.
+
+NOTE 2: Broadcasting Warning Notification Area(s) is not supported in NB-IoT terrestrial network.
+
+## 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 Notifications shall be broadcast to a Notification Area which is based on the geographical information as specified by the Warning Notification Provider.
+- PWS capable UEs (PWS-UE) in idle mode shall be capable of receiving broadcasted Warning Notifications.
+
+NOTE 1: A bandwidth reduced low complexity UE, an NB-IoT UE or a UE supporting eDRX does not necessarily meet all requirements for PWS, including ETWS, CMAS, EU-Alert and KPAS
+
+- PWS shall only be required to broadcast Warning Notifications in languages as prescribed by regulatory requirements.
+- Warning Notifications are processed by PWS on a first in, first out basis, subject to regulatory requirements.
+- Reception and presentation of Warning Notifications to the user shall not pre-empt an active voice or data session.
+- Warning Notifications shall be limited to those emergencies where life or property is at imminent risk, and some responsive action should be taken.
+
+NOTE 2: This requirement does not prohibit the use of the operator's network (i.e. broadcast technology) implemented for Warning Notifications to be used for commercial services.
+
+## 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 Agency
+
+Additional elements may be present, based on regulatory requirements.
+
+There is a concern that URLs or telephone numbers in a Warning Notification could exacerbate wireless network congestion at a time when network traffic is already dramatically increasing as individuals contact police, fire, and rescue personnel, as well as their loved ones. Therefore, Warning Notifications should not contain anything that would drive immediate and debilitating traffic loads into the PLMN (i.e., URLs or dialable numbers) unless required by regional regulation.
+
+## 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 distribution of cells, Node Bs, RNCs, etc.
+
+## 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 Providers.
+
+- Cancellation of Warning Notification delivery
+
+A cancellation is a command from the Warning Notification Provider to stop dissemination of a specific Warning Notification.
+
+- Updating of Warning Notification delivery
+
+Warning Notification Providers update a previous Warning Notification to provide new instructions/information to the PLMN operator. When the Warning Notification Provider updates a previous Warning Notification they provide an identifier that allows the PLMN operator to associate the updated Warning Notification with the previous Warning Notification.
+
+Additional functionality may be required based on regulatory or operator policy requirements.
+
+## 4.6 PWS-UE Requirements
+
+### 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 operator's network or the UE.
+
+It shall be possible for the Warning Notification to be displayed on the PWS-UE upon reception and without any user interaction.
+
+It shall be possible for users to configure the behavior of a PWS-UE with regard to Warning Notification alerting and should allow at least volume adjustment.
+
+The PWS-UE shall support a dedicated alerting indication (audio attention signal and a dedicated vibration cadence) and be distinct from any other device alerts and restricted to use for Warning Notification purposes. The User Interface shall support the ability for the user to suppress the dedicated audio attention signal and/or the dedicated vibration cadence when a Warning Notification is received.
+
+The alerting indication for a specific Warning Notification shall continue until suppressed by users' manual operation (e.g. by pushing keys). The frequency and duration of the continued alerting indication is mobile device implementation specific. This shall not suppress the alerting indication for subsequent Warning Notifications.
+
+The PWS-UE shall automatically suppress duplicate notifications. A duplicate is a repetition of a previous notification as determined by unique parameters.
+
+The PWS-UE shall not support any capabilities to forward received Warning Notifications, to reply to received Warning Notifications, or to copy and paste the content of Warning Notifications.
+
+PWS-UEs should have the ability to present previously displayed Warning Notifications if requested by the user.
+
+- PWS-UE shall be able to support concurrent reception of multiple Warning Notifications.
+
+### 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.
+
+### 4.6.3 Battery Life of PWS-UE
+
+Battery life of the PWS-UE shall not be significantly reduced by PWS.
+
+### 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 User Interface to disable, or later enable, the PWS-UE behavior in response to some or all Warning Notifications. Depending on the regional/regulatory requirements, the user shall be able to receive Warning Notifications in one or more selected languages.
+
+Where regional or national regulations allow, the HPLMN operator shall be able to instruct the PWS-UE to ignore all Warning Notifications in the HPLMN and in PLMNs equivalent to it, by means of a setting on the USIM.
+
+Where regional or national regulations pertaining to a VPLMN allow, the HPLMN operator shall be able to instruct the PWS-UE to ignore all Warning Notifications that are received whilst in this VPLMN, by means of a setting on the USIM, when the integrity of Warning Notifications in this VPLMN is known by the HPLMN operator to be compromised. This setting need not distinguish VPLMNs.
+
+Subject to regional or national regulations, a PWS-UE in limited service state shall be able to receive and display Warning Notifications.
+
+NOTE 1: Non-existing or empty USIM data files results in all Warning Notifications being presented to the PWS application.
+
+NOTE 2: (void).
+
+## 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 section 4.9 for roaming impacts to PWS due to regional regulatory requirements.
+
+## 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 protected. If no such regulatory requirement exists, there shall be no integrity protection of Warning Notifications, and all Warning Notifications shall be presented to the PWS application on the PWS-UE.
+- When required by regional or national regulations, the PWS shall protect against false Warning Notification messages. If no such regulatory requirement exists, there shall be no protection against false Warning Notifications, and all Warning Notifications shall be presented to the PWS application on the PWS-UE.
+
+NOTE 1: These requirements are subject to regulatory policies.
+
+NOTE 2: The authentication and authorisation of the source are outside the scope of 3GPP Specifications.
+
+## 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.
+
+# 5 Earthquake and Tsunami Warning System
+
+## 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 is very short. The order of the duration time is around seconds or minutes at most. Therefore the Warning Notifications shall be delivered quickly to the users in the emergency impacted area so that they could take any actions to escape from danger.
+
+- Accurate Warning Notification delivery.
+
+Warning Notification delivery urges the users to take the actions such as evacuation. Therefore, the Warning Notification shall be delivered to the users accurately in the Notification Area and the content of Warning Notification should be understandable for many types of users (i.e. impaired persons, foreigners).
+
+## 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 required:
+
+- Primary Notification shall be delivered within 4 seconds to the UE in the Notification Area even under congestion situation.
+- Secondary Notification is delivered to the users in the Notification Area even under congestion situation.
+
+NOTE 1: UEs that are out of coverage or switched off are not considered in the requirements.
+
+NOTE 2: Secondary Notification may not always be generated as it depends on the Warning Notification Provider's policy.
+
+NOTE 3: Primary Notification may not always be generated (i.e. the warning may start with a Secondary Notification).
+
+## 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, (e.g. whether to display text in the foreground, whether to ring a buzzer, whether to vibrate);
+- be distinguishable from notifications generated for the purpose of testing, training and other notification services;
+- be sent in an optimized type and amount of data, for example, a text with a certain length, by considering the delivery platforms for ETWS.
+
+Primary Notification shall:
+
+- convey data which is small enough to be sent quickly on the network.
+- convey small amount of data to indicate the imminent occurrence of Earthquake and Tsunami, etc.
+
+Secondary Notification may:
+
+- convey a large amount of data in order to deliver text, audio to instruct what to do / where to get help, graphical data such as a map indicating the route from present position to evacuation site, time table of food distribution.
+
+NOTE: The amount of data to be sent within a Primary Notification would be a few bytes to achieve quick information delivery.
+
+## 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 time in PLMN.
+
+## 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 Provider will send the Warning Notification in the languages in common use in the specific area or in such a way that the Warning Notification can reasonably be understood.
+
+## 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 shall present the received ETWS Notification(s) (Primary or Secondary) if there is a corresponding Warning Notification Area(s) and if the ETWS-capable UE is able to determine that its location is within the corresponding Warning Notification Area(s). Otherwise, if an ETWS-capable UE is unable to or fails to determine its location, the ETWS-capable UE shall present the ETWS Notification(s) (Primary or Secondary) to the user.
+
+## 6 CMAS Specific Requirements
+
+### 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 for the Commercial Mobile Alert System. [1], [2], [3], [8] and [10].
+
+As a result of these legislative and regulatory actions the Alliance for Telecommunications Industry Solutions (ATIS) and the Telecommunications Industry Association (TIA) agreed to develop ATIS and TIA standards to support the deployment of CMAS. This standard is listed in Clause 2.
+
+The scope of these specifications includes the support of Commercial Mobile Alert System (CMAS) alert message via the GSM/UMTS Cell Broadcast functionality and warning message delivery via E-UTRAN, Satellite E-UTRAN, NG-RAN and Satellite NG-RAN. These specifications cover the mapping of CMAS messages onto the 3GPP-defined Cell Broadcast functionality and warning message delivery functionality, as well as the CMAS application layer functionality from the reception of the CMAS alert message from the Warning Notification Provider to the point of reception by the CMAS capable mobile device.
+
+The CMAS functionality does not require modifications to the 3GPP-defined cell broadcast functionality.
+
+The following functional reference model is based on the diagram from Section III.B.10 of the FCC First Report and Order for the Commercial Mobile Alert System, FCC 08-99 [1]:
+
+![Figure 6.1-1: CMAS Reference Architecture diagram showing the flow from Federal Agencies and EOCs through an Alert Aggregator and Gateway to PLMN Infrastructure and Mobile Devices.](b9ecbc3baefab13719e000faa6e0c7eb_img.jpg)
+
+The diagram illustrates the CMAS Reference Architecture, divided into three main sections: A, B, and C. Section A, labeled 'Proposed Government Administered', contains 'Federal Agencies', 'Local EOC', and 'State EOC'. These entities connect to an 'Alert Aggregator' (represented by a cloud icon) within Section B. Section B also contains an 'Alert Gateway' (represented by a server rack icon). The 'Alert Gateway' connects to Section C, which is labeled 'PLMN Gateway' and contains 'PLMN Infrastructure' (represented by a tower icon) and 'Mobile Device' (represented by a smartphone icon). The flow is indicated by dashed lines and arrows, showing the path from the government-administered entities through the aggregator and gateway to the mobile devices. Labels D and E are also present in section C, corresponding to the PLMN Infrastructure and Mobile Device respectively.
+
+Figure 6.1-1: CMAS Reference Architecture diagram showing the flow from Federal Agencies and EOCs through an Alert Aggregator and Gateway to PLMN Infrastructure and Mobile Devices.
+
+**Figure 6.1-1: CMAS Reference Architecture**
+
+## 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 7 bit Default Alphabet [9] for E-UTRAN, Satellite E-UTRAN, NG-RAN and Satellite NG-RAN.
+
+The following classes of Warning Notifications shall be supported: Presidential, Imminent Threat, Public Safety, Child Abduction Emergency (e.g. AMBER), and State/Local WEA Test.
+
+When a Presidential Warning Notification is received, it shall always be presented to the user whenever Cell Broadcast Service via GSM, UMTS or warning notification delivery via E-UTRAN, Satellite E-UTRAN, NG-RAN and Satellite NG-RAN is enabled on the UE.
+
+If the Presidential Warning Notification is received in English, then it shall be displayed by the UE. If the Presidential Warning Notification is received in a language other than English, then it shall only be displayed by the UE if the User has selected that language.
+
+A CMAS-capable User Interface (UI) shall support the ability for the user to opt-out of only the Imminent Threat, Public Safety and Child Abduction Emergency Warning Notifications. A CMAS-capable User Interface (UI) shall support the ability for the user to opt-in to the State/Local WEA Test notification.
+
+If the User has opted out of a Warning Notification class, then the Warning Notification for that class shall not be displayed by the UE.
+
+If the User has not opted out of a Warning Notification class, then any Warning Notifications for that class received in English shall be displayed by the UE. This also applies to Warning Notifications received in any additional languages that may be selected by the User.
+
+Warning Notifications may contain URLs and/or phone numbers.
+
+A CMAS-capable User Interface (UI) shall support the ability (e.g., a ‘‘click’’ touch input) for the user to navigate to the URL or initiate a voice call to the phone number which may be included in the Warning Notification [8].
+
+The PLMN broadcasting CMAS Warning Notifications shall also broadcast corresponding CMAS Warning Notification Area(s) when the CMAS Warning Notification is required to adhere to the maximum 0,1 of a mile CMAS Warning Notification Area(s) overshooting as specified in [10]. This requirement applies only to LTE and NR accesses.
+
+A CMAS-capable UE shall utilize UE-Based Location Calculation (see 3GPP TS 22.071 [11]) to determine whether it is located within the corresponding CMAS Warning Notification Area(s) in order to minimize overloading network LCS resources.
+
+Subject to opt-out and opt-in settings described above, a CMAS-capable UE shall present the CMAS Warning Notification sent if there is a corresponding CMAS Warning Notification Area(s) and if the CMAS-capable UE is able to determine that its location is within the corresponding CMAS Warning Notification Area(s). Otherwise, if a CMAS-capable UE is unable to or fails to determine its location, the CMAS-capable UE shall present the Warning Notification to the user.
+
+A CMAS-capable UE shall store presented Warning Notifications for at least 24 hours unless explicitly deleted by the user.
+
+---
+
+## 7 EU-ALERT Specific Requirements
+
+### 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 meet their specific national requirements whilst adhering to a common core specification.
+
+### 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 imminent emergency situation, Advisory messages of lesser urgency, and Amber alerts.
+
+The Alert messages shall be supported with three levels of severity. EU-Alert level 1 shall have no opt-out; levels 2 and 3 shall allow opt-out by the user. All levels of EU-ALERT messages shall be associated with a dedicated alerting indication.
+
+NOTE: EU-Alert level 1 is compatible with the Presidential Alert in CMAS. EU-Alert level 2 is compatible with CMAS Extreme Alerts and EU-Alert level 3 is compatible with CMAS Severe Alert.
+
+The Advisory messages have only one level. Advisory messages shall not be associated with any dedicated alerting indication.
+
+Depending on national requirements, Amber alerts may need to be broadcast as part of the EU-ALERT service. Amber alerts shall not be associated with any dedicated alerting indication.
+
+EU-ALERT shall support Warning Notifications in various languages. To support international roaming, it is expected that countries adopting EU-ALERT use the same Message Identifier for Warning Notifications in the local language. If Warning Notifications are broadcast in other languages besides the local language, then the Message Identifier for such Warning Notifications are expected to be the same across the countries adopting EU-ALERT.
+
+EU-ALERT shall be supported on GERAN, UTRAN, E-UTRAN, Satellite E-UTRAN, NG-RAN, and Satellite NG-RAN.
+
+EU-ALERT shall support that the PLMN broadcasting EU-ALERT Warning Notifications also broadcasts corresponding Warning Notification Area(s). This requirement applies only to E-UTRAN, Satellite E-UTRAN, NG-RAN and Satellite NG-RAN.
+
+A EU-ALERT-capable UE shall utilize UE-Based Location Calculation (see 3GPP TS 22.071 [11]) to determine whether it is located within the corresponding Warning Notification Area(s) in order to minimize overloading network LCS resources.
+
+Subject to opt-out and opt-in settings described above, a EU-ALERT-capable UE shall present the EU-ALERT Warning Notification sent if there is a corresponding Warning Notification Area(s) and if the EU-ALERT-capable UE is able to determine that its location is within the corresponding Warning Notification Area(s). Otherwise, if a EU-ALERT-capable UE is unable to or fails to determine its location, the EU-ALERT-capable UE shall present the EU-ALERT Warning Notification to the user.
+
+---
+
+## 8 Korean Public Alert System specific Requirements
+
+### 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] also specifies application layer functionality to handle the transmission of CBS data from CBE to CBC and support for transmission of the same public alert message to UEs belonging to different mobile network operators in Republic of Korea. The specification requires that the system supporting Korean Public Alert System (KPAS) shall transmit the public alert message with high priority in order to provide up-to-date information on emergency situations. (e.g. In Tsunami situation, it is recommended to deliver message between CBC and UE in several seconds.).
+
+### 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 class 1 shall allow opt-out by the user.
+
+Different types of Warning Notification shall be supported: Extreme Emergency, Emergency, Public Safety, and Amber. The Extreme Emergency type Warning Notifications are defined as class 0 and the other types are defined as class 1.
+
+The characteristics of the Warning Notification shall follow the requirements specified in clause 4.
+
+The current implementation requirement is for the message of up to 90 characters text. In addition, Warning Notifications using the UCS2 coding scheme [9] shall support up to 157 characters and Warning Notifications using the GSM 7 bit Default Alphabet coding scheme [9] shall support up to 360 characters from LTE onwards.
+
+KPAS shall support Warning Notifications in various languages. If a Warning Notification is received in a language other than Korean, then it shall only be displayed by the UE if the user has selected that language.
+
+A PWS-UE shall display Warning Notifications whose first texts are dedicated words when a PWS-UE receives Warning Notifications in other languages than Korean.
+
+NOTE 1: Dedicated words are specified in the regulations of Korean Ministry of Interior and Safety.
+
+A PWS-UE in KPAS shall support two dedicated alerting indication (audio attention signals).
+
+NOTE 2: Two dedicated audio attention signals are specified in the regulations of Korean Ministry of Interior and Safety.
+
+Warning Notifications may contain URLs and/or phone numbers. A UE shall allow the user to navigate to the URL or initiate a voice call to the phone number which may be included in the Warning Notification.
+
+KPAS shall support that the PLMN broadcasting KPAS Warning Notifications also broadcasts corresponding Warning Notification Area(s).
+
+A KPAS-capable UE shall utilize UE-Based Location Calculation (see 3GPP TS 22.071 [11]) to determine whether it is located within the corresponding Warning Notification Area(s) in order to minimize overloading network LCS resources.
+
+Subject to opt-out and opt-in settings described above, a KPAS-capable UE shall present the KPAS Warning Notification sent if there is a corresponding Warning Notification Area(s) and if the KPAS-capable UE is able to determine that its location is within the corresponding Warning Notification Area(s). Otherwise, if a KPAS-capable UE is unable to or fails to determine its location, the KPAS-capable UE shall present the KPAS Warning Notification to the user.
+
+---
+
+## 9 Enhancements of Public Warning System (ePWS)
+
+### 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, enhancements of Public Warning System (ePWS) is intended to improve the comprehension of a Warning Notification to the following categories of users:
+
+- Users with disabilities who have UEs supporting assistive technologies beyond text assistive technologies; and
+- Users who are not fluent in the language of the Warning Notifications.
+
+Requirements defined for PWS-UEs in clause 4 are applicable for ePWS-UEs unless dedicated ePWS-UE requirements described in clause 9 supersede them. Specifically, roaming requirements specified in clause 4.7 and security requirements specified in clause 4.8 are applicable for ePWS-UEs.
+
+### 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 translation in the operator's network or the UE.
+
+It shall be possible for the Warning Notification to be presented on the ePWS-UE upon reception and without any user interaction.
+
+It shall be possible for users to configure the behavior of an ePWS-UE with regard to Warning Notification alerting and should allow at least volume adjustment if an ePWS-UE supports the alerting sound.
+
+ePWS-UEs should have the ability to present previously displayed Warning Notifications if requested by the user.
+
+- ePWS-UE shall be able to support concurrent reception of multiple Warning Notifications.
+
+#### 9.2.2 Battery Life of ePWS-UE
+
+Battery life of the ePWS-UE shall not be significantly reduced by ePWS.
+
+#### 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 the user interface to disable, or later enable, the ePWS-UE behavior in response to some or all Warning Notifications. Depending on the regional/regulatory requirements, the user shall be able to receive Warning Notifications in one or more selected languages.
+
+Where regional or national regulations allow, the HPLMN operator shall be able to instruct the ePWS-UE to ignore all Warning Notifications in the HPLMN and in PLMNs equivalent to it, by means of a setting on the USIM.
+
+Where regional or national regulations pertaining to a VPLMN allow, the HPLMN operator shall be able to instruct the ePWS-UE to ignore all Warning Notifications that are received whilst in this VPLMN, by means of a setting on the USIM, when the integrity of Warning Notifications in this VPLMN is known by the HPLMN operator to be compromised. This setting need not distinguish VPLMNs.
+
+Subject to regional or national regulations, a ePWS-UE in limited service state shall be able to receive and present Warning Notifications.
+
+NOTE : Non-existing or empty USIM data files results in all Warning Notifications being presented to the ePWS application.
+
+## **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.
+
+## **9.4 Requirements for ePWS-UE incapable of displaying text based Warning Notification**
+
+### **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 consistent with the ePWS-UE function (e.g. IoT) in response to specific Warning Notifications based on the content of the Warning Notification, e.g. shut down machinery or trigger a building alarm system.
+
+### **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 Notification.
+
+NOTE: The information extractable from the received Warning Notification may be an identifier of an event or a disaster.
+
+## **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 to support the extraction of any information on the type of a PWS notified event or disaster from the received Warning Notification
+
+The ePWS-UE with a user interface providing accessibility extensions to mobile users with disabilities shall support the presentation of the information that improves the comprehension of Warning Notification by the accessibility extensions.
+
+NOTE: Subject to regional regulatory requirements the ePWS-UE may use alternative alerting modes for user alerting consistent with ePWS-UE accessibility extensions and based on the content of the Warning Notification.
+
+A PWS-UE may support the extraction and presentation of information representing a disaster or an event identifiable by Warning Notifications.
+
+---
+
+## 10 Relay of Warning Notification
+
+### 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 specified in the clause 10 when receiving a Warning Notification via the relay functionality.
+
+### 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 notification as determined by unique parameters.
+
+A remote ePWS-UE and a remote PWS-UE receiving a Warning Notification transmitted via an UE that supports the relay functionality shall behave in the same fashion as if it received the message directly from a 3GPP network.
+
+An UE that supports the relay functionality shall unconditionally forward the Warning Notification broadcast received from the network.
+
+---
+
+## 11 Chinese Public Alert System Specific Requirements
+
+### 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.
+
+### 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 Communications Standards Association (CCSA). Four message levels (Level 1 - Level 4), with one or more message identifiers per level, have been defined by CCSA.